Transaction
Transfers, deploys, calls, PoTB types
Pre-mainnet
RevertedContract call
- Transaction hash
- Signing hash
- Block
- 59,412,4784m ago
- Timestamp
- 2026-01-14 23:55:54 UTC
- Amount
- —
- Fee
- 0.00940416 LUNE
- Gas used
- 78,368 / 119,18365.8%
- Nonce
- 2831
- Chain ID
- astrolune-testnet-4
- Public key
- Signature
- fc37c49486a08a8a16b01ce01b7af92e71362f384d6ed88fa8f2a1167bef1efdea0b9db88a13bc20a8f48894e512e8561ae9209d2cbb99944fa8425d79f917d4
- Payload
- 0x076eeb6a494f3c13fb32c48b35e165c7ce40ff1a3c4a5ca072c603feeb8b86
The transaction identifier and the signed message are hashed under different domain tags on purpose, so a signature over one can never be mistaken for a signature over the other.
The signature layer currently compiled into the core is a deliberate stub. Signatures are trivially forgeable. Do not put value on any Astrolune network yet.