Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be685df43dae285fbf68146e97b5febb18d09f3828c1ed1ade0899351ef1bc8f

Tx prefix hash: d1391aed1c3f07188fe415900249f1578b61ca38d534a4f73c0fd7056257aaeb
Tx public key: fd6e66a6a2b72d89f93d174763630214671ee0b1fdf5e8df763052c95d178d93
Timestamp: 1736847131 Timestamp [UCT]: 2025-01-14 09:32:11 Age [y:d:h:m:s]: 00:059:03:03:53
Block: 1197087 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 42045 RingCT/type: yes/0
Extra: 01fd6e66a6a2b72d89f93d174763630214671ee0b1fdf5e8df763052c95d178d930211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8d3d00fbdedb029c44c88788cde28aaf86d32f1d2c23851102faf5ca6094e737 0.600000000000 1683692 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": 1197097, "vin": [ { "gen": { "height": 1197087 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8d3d00fbdedb029c44c88788cde28aaf86d32f1d2c23851102faf5ca6094e737" } } ], "extra": [ 1, 253, 110, 102, 166, 162, 183, 45, 137, 249, 61, 23, 71, 99, 99, 2, 20, 103, 30, 224, 177, 253, 245, 232, 223, 118, 48, 82, 201, 93, 23, 141, 147, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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