Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 97bd3c22e02affeee1e4610302124d50c4a882f695147b3bcae10e7ee7f04168

Tx prefix hash: 3eaf1e1c4ea14f10c8a6cfca867c02c03c380a9fa3739366ac47e23e4c3f919b
Tx public key: a72effeff67537b1d9aad20a4b574492a53ef08a508e8e367fff2fb6d5ea36f3
Timestamp: 1727328927 Timestamp [UCT]: 2024-09-26 05:35:27 Age [y:d:h:m:s]: 00:118:22:33:02
Block: 1118316 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85000 RingCT/type: yes/0
Extra: 01a72effeff67537b1d9aad20a4b574492a53ef08a508e8e367fff2fb6d5ea36f3021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 70baf22bea57d1bddf6566b8f7ab7c1c29f118bf5f45756efb5f19f903203800 0.600000000000 1599467 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": 1118326, "vin": [ { "gen": { "height": 1118316 } } ], "vout": [ { "amount": 600000000, "target": { "key": "70baf22bea57d1bddf6566b8f7ab7c1c29f118bf5f45756efb5f19f903203800" } } ], "extra": [ 1, 167, 46, 255, 239, 246, 117, 55, 177, 217, 170, 210, 10, 75, 87, 68, 146, 165, 62, 240, 138, 80, 142, 142, 54, 127, 255, 47, 182, 213, 234, 54, 243, 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