Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d87f9f19c54ff0cd023fad3970dd8bf2bd948da98e71d04100e13d2c0132c7d8

Tx prefix hash: 59d9568e95ba8483153b5de2b9f1495dda0fc32153cdb3b0d731a2098b6e4bc4
Tx public key: 858c6e1f333e54a9629f8fb28101e30b7dbbacb1242bf23dc4306d84101cb3db
Timestamp: 1761564555 Timestamp [UCT]: 2025-10-27 11:29:15 Age [y:d:h:m:s]: 00:018:13:46:50
Block: 1399037 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 13288 RingCT/type: yes/0
Extra: 01858c6e1f333e54a9629f8fb28101e30b7dbbacb1242bf23dc4306d84101cb3db02110000000ddfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c322946501b4b22f31a45b41694c12f8175c8c33ae606c7ccc9dcc027a7be252 0.600000000000 1887340 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": 1399047, "vin": [ { "gen": { "height": 1399037 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c322946501b4b22f31a45b41694c12f8175c8c33ae606c7ccc9dcc027a7be252" } } ], "extra": [ 1, 133, 140, 110, 31, 51, 62, 84, 169, 98, 159, 143, 178, 129, 1, 227, 11, 125, 187, 172, 177, 36, 43, 242, 61, 196, 48, 109, 132, 16, 28, 179, 219, 2, 17, 0, 0, 0, 13, 223, 195, 186, 73, 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