Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ce4108d0ca39fd23d152e2ce3035f28633b5e610cdc1da77b8e869fe0e3dd24c

Tx prefix hash: 06d4966c54353bb383bd4fd2746c929d2be4b7d2bfce692fb44f8334de4499af
Tx public key: 9ef3294227cae9a37fb73de6bef41ee3d343edff0f6dde2563ed2b00007d7cd9
Timestamp: 1581570937 Timestamp [UCT]: 2020-02-13 05:15:37 Age [y:d:h:m:s]: 05:089:00:40:12
Block: 63938 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1216456 RingCT/type: yes/0
Extra: 019ef3294227cae9a37fb73de6bef41ee3d343edff0f6dde2563ed2b00007d7cd902110000000256c366d3000000000000000000

1 output(s) for total of 376.831914378000 dcy

stealth address amount amount idx
00: 5f415731689444e1bdcad73dfa1f0be3e76c16790be302bda0bf4ef1e22503c9 376.831914378000 117845 of 0

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": 63948, "vin": [ { "gen": { "height": 63938 } } ], "vout": [ { "amount": 376831914378, "target": { "key": "5f415731689444e1bdcad73dfa1f0be3e76c16790be302bda0bf4ef1e22503c9" } } ], "extra": [ 1, 158, 243, 41, 66, 39, 202, 233, 163, 127, 183, 61, 230, 190, 244, 30, 227, 211, 67, 237, 255, 15, 109, 222, 37, 99, 237, 43, 0, 0, 125, 124, 217, 2, 17, 0, 0, 0, 2, 86, 195, 102, 211, 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