Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2daa564cb8f6878d5e3b9e3f8f62675f3f35ce09c1553a5cc7a999bacca38934

Tx prefix hash: 7346f7f9c0d1622e8c1f9d552e4c36b270e80ae9581cc376455f4baf8bf9f9da
Tx public key: 221e2864e3906d19f70e1a1b40b845d4ad96417f7e92d0062d1ffe7890e22853
Timestamp: 1710625148 Timestamp [UCT]: 2024-03-16 21:39:08 Age [y:d:h:m:s]: 01:239:18:36:34
Block: 979855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 430054 RingCT/type: yes/0
Extra: 01221e2864e3906d19f70e1a1b40b845d4ad96417f7e92d0062d1ffe7890e2285302110000000d7a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 32abc0c0a376ddb225b8f2703df0997d15752ffdf3a1360ab2c922a2922e9523 0.600000000000 1439910 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": 979865, "vin": [ { "gen": { "height": 979855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "32abc0c0a376ddb225b8f2703df0997d15752ffdf3a1360ab2c922a2922e9523" } } ], "extra": [ 1, 34, 30, 40, 100, 227, 144, 109, 25, 247, 14, 26, 27, 64, 184, 69, 212, 173, 150, 65, 127, 126, 146, 208, 6, 45, 31, 254, 120, 144, 226, 40, 83, 2, 17, 0, 0, 0, 13, 122, 156, 244, 199, 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