Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b40a119c261281b9e67c7e2d3a00cac12f7663e477748acff357a0a4f0b4d10f

Tx prefix hash: d985c133c080d0a4f5e726db4a91dd14365f24c1ccf4aa894abdc75e58f1b7a4
Tx public key: 20859bcb6b300e1d41ca377c8df94e876fd7c6a7a2dbb3fed084beb0323413e5
Timestamp: 1760988760 Timestamp [UCT]: 2025-10-20 19:32:40 Age [y:d:h:m:s]: 00:063:18:30:12
Block: 1394277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 45626 RingCT/type: yes/0
Extra: 0120859bcb6b300e1d41ca377c8df94e876fd7c6a7a2dbb3fed084beb0323413e5021100000004dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9aab8dc1bcbe674b4ac50a5668d3296b2435bcffeb6b70e9b337fe29ec25060e 0.600000000000 1882548 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": 1394287, "vin": [ { "gen": { "height": 1394277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9aab8dc1bcbe674b4ac50a5668d3296b2435bcffeb6b70e9b337fe29ec25060e" } } ], "extra": [ 1, 32, 133, 155, 203, 107, 48, 14, 29, 65, 202, 55, 124, 141, 249, 78, 135, 111, 215, 198, 167, 162, 219, 179, 254, 208, 132, 190, 176, 50, 52, 19, 229, 2, 17, 0, 0, 0, 4, 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