Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 303a40e9556eb269b400fd7f14a4c42c182de1a11c3c7e49fc8a313a1885dc1b

Tx prefix hash: 4ddd4dfe92afd8391e83f64b94753eb2c6a32e249690aa5f75c4ff887ba9f290
Tx public key: 5965abcd4a636978704de8aef5e8b4b26c6c2f995047305c65efde887b06573c
Timestamp: 1750138790 Timestamp [UCT]: 2025-06-17 05:39:50 Age [y:d:h:m:s]: 00:157:04:52:48
Block: 1306748 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 110141 RingCT/type: yes/0
Extra: 015965abcd4a636978704de8aef5e8b4b26c6c2f995047305c65efde887b06573c021100000008bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5bd8ec5ab991e363fb1635b42f17607faa7ed9d6fc762c0e21ee7898e283151 0.600000000000 1794357 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": 1306758, "vin": [ { "gen": { "height": 1306748 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5bd8ec5ab991e363fb1635b42f17607faa7ed9d6fc762c0e21ee7898e283151" } } ], "extra": [ 1, 89, 101, 171, 205, 74, 99, 105, 120, 112, 77, 232, 174, 245, 232, 180, 178, 108, 108, 47, 153, 80, 71, 48, 92, 101, 239, 222, 136, 123, 6, 87, 60, 2, 17, 0, 0, 0, 8, 191, 81, 178, 162, 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