Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5437f1678bb1f67034123c1e173d0e525226a5ff73c479f79e4be87a0d7a66da

Tx prefix hash: c764c5fccb851b540cbf7010de1185e3f3bf32ecc53918aef7db97aa299e2ce8
Tx public key: c33407fc15e8dcb715fec2a54a239d5dea89254b42b0444ec6ce4799fc4dbe20
Timestamp: 1765156420 Timestamp [UCT]: 2025-12-08 01:13:40 Age [y:d:h:m:s]: 00:054:14:41:45
Block: 1428789 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 38933 RingCT/type: yes/0
Extra: 01c33407fc15e8dcb715fec2a54a239d5dea89254b42b0444ec6ce4799fc4dbe2002110000000370609d03000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3a4d5b912d755b524ba23fc79b9ea36ca6613fd6d1ab62ebbdffb19758c96338 0.600000000000 1917512 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": 1428799, "vin": [ { "gen": { "height": 1428789 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3a4d5b912d755b524ba23fc79b9ea36ca6613fd6d1ab62ebbdffb19758c96338" } } ], "extra": [ 1, 195, 52, 7, 252, 21, 232, 220, 183, 21, 254, 194, 165, 74, 35, 157, 93, 234, 137, 37, 75, 66, 176, 68, 78, 198, 206, 71, 153, 252, 77, 190, 32, 2, 17, 0, 0, 0, 3, 112, 96, 157, 3, 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