Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cb2b24e4eb8b8aef710a3ea93c84c93dbfed113fa54593ebeb859946fea18659

Tx prefix hash: 10fd33d913d9b6d8a7be3414f3e5d91667caec21e9012d22740425d5a0ead917
Tx public key: 81117c8c35216e98ff63720a88ef7a7a9df8db160c96047747a14f46133cf3d8
Timestamp: 1749797566 Timestamp [UCT]: 2025-06-13 06:52:46 Age [y:d:h:m:s]: 00:160:17:33:39
Block: 1303977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112605 RingCT/type: yes/0
Extra: 0181117c8c35216e98ff63720a88ef7a7a9df8db160c96047747a14f46133cf3d802110000000201491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 90c87f0e7f8fa2eb83d7f02e12654a6400b905b57fb2c6948382376a9423c1c0 0.600000000000 1791562 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": 1303987, "vin": [ { "gen": { "height": 1303977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "90c87f0e7f8fa2eb83d7f02e12654a6400b905b57fb2c6948382376a9423c1c0" } } ], "extra": [ 1, 129, 17, 124, 140, 53, 33, 110, 152, 255, 99, 114, 10, 136, 239, 122, 122, 157, 248, 219, 22, 12, 150, 4, 119, 71, 161, 79, 70, 19, 60, 243, 216, 2, 17, 0, 0, 0, 2, 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