Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a58da4c4f482e2bd5eedf7b0ab03e1c3cfa3cb41fe8a59f4cf1a69889939c629

Tx prefix hash: eeb37d3b4ada67251cd214baa55859662f689eb507febc058ca9726c75b6286c
Tx public key: c9fd96698e7484f0a41921a0a1b94ac8f87d620dbfba6488c438c4cfbd50b118
Timestamp: 1755303749 Timestamp [UCT]: 2025-08-16 00:22:29 Age [y:d:h:m:s]: 00:133:20:52:39
Block: 1347517 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 95477 RingCT/type: yes/0
Extra: 01c9fd96698e7484f0a41921a0a1b94ac8f87d620dbfba6488c438c4cfbd50b11802110000000425a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4729404ed0f5a5484605e7db44f90b1ce30175eddefac23d58dc4c3dae8b39ad 0.600000000000 1835434 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": 1347527, "vin": [ { "gen": { "height": 1347517 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4729404ed0f5a5484605e7db44f90b1ce30175eddefac23d58dc4c3dae8b39ad" } } ], "extra": [ 1, 201, 253, 150, 105, 142, 116, 132, 240, 164, 25, 33, 160, 161, 185, 74, 200, 248, 125, 98, 13, 191, 186, 100, 136, 196, 56, 196, 207, 189, 80, 177, 24, 2, 17, 0, 0, 0, 4, 37, 163, 90, 15, 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