Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 59569ba51ad515eb4f46da0411dcd698e2c84efd4d4b849170b2353bb2c88106

Tx prefix hash: c54a68a286429f6a4b922f81dc7c8138c3212b21aad88637e31923b938793266
Tx public key: 07c31a36e8c1fb769fe7add139d455fc06f02dd1fd8df386df92c1f4c856b9fa
Timestamp: 1763180410 Timestamp [UCT]: 2025-11-15 04:20:10 Age [y:d:h:m:s]: 00:006:09:49:31
Block: 1412416 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 4579 RingCT/type: yes/0
Extra: 0107c31a36e8c1fb769fe7add139d455fc06f02dd1fd8df386df92c1f4c856b9fa02110000000801491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ad30252a40396cb53db6f0e4a3506968af7416cfcddf2a342ac185112f603d5e 0.600000000000 1900885 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": 1412426, "vin": [ { "gen": { "height": 1412416 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ad30252a40396cb53db6f0e4a3506968af7416cfcddf2a342ac185112f603d5e" } } ], "extra": [ 1, 7, 195, 26, 54, 232, 193, 251, 118, 159, 231, 173, 209, 57, 212, 85, 252, 6, 240, 45, 209, 253, 141, 243, 134, 223, 146, 193, 244, 200, 86, 185, 250, 2, 17, 0, 0, 0, 8, 1, 73, 31, 136, 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