Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3c0f67d7b32cc64d73a7b150551a737ad7f696ef8d3ee7c8dcb8bb39180708bf

Tx prefix hash: 466506703a17ec339935fe264fe738d75177e57003a7dc9e2658b0a5ff9e005e
Tx public key: 73acb31a981b14e92b6722a3f7076398e3e100e9bfe66e2ce24dd2c66b9af3e1
Timestamp: 1703960607 Timestamp [UCT]: 2023-12-30 18:23:27 Age [y:d:h:m:s]: 01:342:05:39:22
Block: 924570 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 503468 RingCT/type: yes/0
Extra: 0173acb31a981b14e92b6722a3f7076398e3e100e9bfe66e2ce24dd2c66b9af3e102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6a982273a86b7c022edc67d6a6a56ff9701860d60ad8f3895cb64c9b3b4b7418 0.600000000000 1382324 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": 924580, "vin": [ { "gen": { "height": 924570 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6a982273a86b7c022edc67d6a6a56ff9701860d60ad8f3895cb64c9b3b4b7418" } } ], "extra": [ 1, 115, 172, 179, 26, 152, 27, 20, 233, 43, 103, 34, 163, 247, 7, 99, 152, 227, 225, 0, 233, 191, 230, 110, 44, 226, 77, 210, 198, 107, 154, 243, 225, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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