Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82a7a1f12d47c0c1b81b50e8cb9a61d550fb2716052b755707b30b31deab5937

Tx prefix hash: 5844543cb215d49c404a9861d1ec0154d135f89c40770ee85d10bd541022170a
Tx public key: 8a089c7b9dac76d3b10b6ccf1f81d84d9fdf7621e6f0b8553718bac704ff4237
Timestamp: 1709312133 Timestamp [UCT]: 2024-03-01 16:55:33 Age [y:d:h:m:s]: 01:074:10:51:37
Block: 968956 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 314235 RingCT/type: yes/0
Extra: 018a089c7b9dac76d3b10b6ccf1f81d84d9fdf7621e6f0b8553718bac704ff423702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 72be4eb6e297764232c21beadaee23feaece467aff822b50c91a075ecf3f9736 0.600000000000 1428783 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": 968966, "vin": [ { "gen": { "height": 968956 } } ], "vout": [ { "amount": 600000000, "target": { "key": "72be4eb6e297764232c21beadaee23feaece467aff822b50c91a075ecf3f9736" } } ], "extra": [ 1, 138, 8, 156, 123, 157, 172, 118, 211, 177, 11, 108, 207, 31, 129, 216, 77, 159, 223, 118, 33, 230, 240, 184, 85, 55, 24, 186, 199, 4, 255, 66, 55, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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