Dinastycoin Explorer Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: efad72f6c1b29d3f329f4c5f6df3e07087c71e4c5d0502f5966ca7b27914b8fe

Tx prefix hash: ec880537100692a45935083329d37c7300f771f11189ed1274783a3dc6223c1f
Tx public key: e3dfce9c378402c80662dafc8de487d67057ab6edd0034a9d1b2869ed13e27f6
Timestamp: 1772978139 Timestamp [UTC]: 2026-03-08 13:55:39 Age [y:d:h:m:s]: 00:259:03:06:52
Block: 1493410 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 190084 RingCT/type: yes/0
Extra: 01e3dfce9c378402c80662dafc8de487d67057ab6edd0034a9d1b2869ed13e27f6021100000003f188c8a8000000000000000000

1 output(s) for total of 0.000600000000 xmr

stealth address amount amount idx tag
00: 7155d4a3ce723b87eaab84c722f3e32e8142b76177395df36ad849dc29969c89 0.000600000000 1982970 of 15 -

Check which outputs belong to given dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinastycoin-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1493420, "vin": [ { "gen": { "height": 1493410 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7155d4a3ce723b87eaab84c722f3e32e8142b76177395df36ad849dc29969c89" } } ], "extra": [ 1, 227, 223, 206, 156, 55, 132, 2, 200, 6, 98, 218, 252, 141, 228, 135, 214, 112, 87, 171, 110, 221, 0, 52, 169, 209, 178, 134, 158, 209, 62, 39, 246, 2, 17, 0, 0, 0, 3, 241, 136, 200, 168, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): devel-2026-02-02-6303d2a (1.2) | monero version: