Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d7e2c671d66e12999ddc9494c52e8f0126636634d709665e92b9a6b60171c397

Tx prefix hash: 38875c7baca0a3da0b83884f83dada5dfd90c54edb6543c310d0168e61c2f982
Tx public key: 9fda6abbb2fa1c848a1fb2c8dcbbe7fe530f73ea808206d6d3925276b49c709f
Timestamp: 1737287018 Timestamp [UCT]: 2025-01-19 11:43:38 Age [y:d:h:m:s]: 00:336:01:07:30
Block: 1200684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237759 RingCT/type: yes/0
Extra: 019fda6abbb2fa1c848a1fb2c8dcbbe7fe530f73ea808206d6d3925276b49c709f021100000004007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d7bccc82eb1437ccd4d3c23afac083be5b748e30f85b1414d317531122d88e5 0.600000000000 1687329 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": 1200694, "vin": [ { "gen": { "height": 1200684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d7bccc82eb1437ccd4d3c23afac083be5b748e30f85b1414d317531122d88e5" } } ], "extra": [ 1, 159, 218, 106, 187, 178, 250, 28, 132, 138, 31, 178, 200, 220, 187, 231, 254, 83, 15, 115, 234, 128, 130, 6, 214, 211, 146, 82, 118, 180, 156, 112, 159, 2, 17, 0, 0, 0, 4, 0, 127, 151, 138, 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