Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8ae2e4a955580a573e1a69c61ecfa30138be7c9c5a81b536c49ebf746b28cb3f

Tx prefix hash: c2e37d1f643593bb7b2191a4b8ed4cf09a7f426e1d73395f8deb59a5c322c531
Tx public key: 2e837478e057fce2c3c10031eb40987d7fa7c6860e6ba5ce28fb708a5830f2bb
Timestamp: 1750024669 Timestamp [UCT]: 2025-06-15 21:57:49 Age [y:d:h:m:s]: 00:158:11:37:29
Block: 1305809 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 111047 RingCT/type: yes/0
Extra: 012e837478e057fce2c3c10031eb40987d7fa7c6860e6ba5ce28fb708a5830f2bb02110000000143846d66000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 878afc1c46414567b4a81be1ac595f5cdce46c72f206aa4ef8f703f1d6810489 0.600000000000 1793410 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 dinasty-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": 1305819, "vin": [ { "gen": { "height": 1305809 } } ], "vout": [ { "amount": 600000000, "target": { "key": "878afc1c46414567b4a81be1ac595f5cdce46c72f206aa4ef8f703f1d6810489" } } ], "extra": [ 1, 46, 131, 116, 120, 224, 87, 252, 226, 195, 193, 0, 49, 235, 64, 152, 125, 127, 167, 198, 134, 14, 107, 165, 206, 40, 251, 112, 138, 88, 48, 242, 187, 2, 17, 0, 0, 0, 1, 67, 132, 109, 102, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8