Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ae98a0565e9ee500f9ea226d8be75a986ed2e34d9e61cd3f53449b4b8ad40f87

Tx prefix hash: 86f6788421f8758d17882d374472c6c8a4aafc1fbeda4126222057e826f31b6b
Tx public key: 1ad2eb129c0430cfefb9ddf84e4bc2bbbcffba5755d5a85830fbd62b27d6f629
Timestamp: 1720508554 Timestamp [UCT]: 2024-07-09 07:02:34 Age [y:d:h:m:s]: 01:120:00:33:27
Block: 1061778 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 344275 RingCT/type: yes/0
Extra: 011ad2eb129c0430cfefb9ddf84e4bc2bbbcffba5755d5a85830fbd62b27d6f629021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a7fb0341732d6dcff8fb97f715cc96fcff808d48fe5230a3aa539e17d82fc1d1 0.600000000000 1532273 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": 1061788, "vin": [ { "gen": { "height": 1061778 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a7fb0341732d6dcff8fb97f715cc96fcff808d48fe5230a3aa539e17d82fc1d1" } } ], "extra": [ 1, 26, 210, 235, 18, 156, 4, 48, 207, 239, 185, 221, 248, 78, 75, 194, 187, 188, 255, 186, 87, 85, 213, 168, 88, 48, 251, 214, 43, 39, 214, 246, 41, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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