Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8352fc098905474667d36217e3429ff2dffd10aced952ae796a56be06c70ba37

Tx prefix hash: 0f1e6cf534ef801770e01b1ed281a15f630b1bce25cc22e5546c2a502fdb74b7
Tx public key: b0a0e36ee5543ced0050462fa2908ee5d46c03e525939d77ee2bf627dd235d67
Timestamp: 1660431259 Timestamp [UCT]: 2022-08-13 22:54:19 Age [y:d:h:m:s]: 02:222:14:01:54
Block: 565254 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 680307 RingCT/type: yes/0
Extra: 01b0a0e36ee5543ced0050462fa2908ee5d46c03e525939d77ee2bf627dd235d67021100000001ec6d1a1a000000000000000000

1 output(s) for total of 8.224031569000 dcy

stealth address amount amount idx
00: bcf33c29b328c1f95a10580b559705ae864ceee63d511e7f1c6728d3e0e1cf9d 8.224031569000 998130 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": 565264, "vin": [ { "gen": { "height": 565254 } } ], "vout": [ { "amount": 8224031569, "target": { "key": "bcf33c29b328c1f95a10580b559705ae864ceee63d511e7f1c6728d3e0e1cf9d" } } ], "extra": [ 1, 176, 160, 227, 110, 229, 84, 60, 237, 0, 80, 70, 47, 162, 144, 142, 229, 212, 108, 3, 229, 37, 147, 157, 119, 238, 43, 246, 39, 221, 35, 93, 103, 2, 17, 0, 0, 0, 1, 236, 109, 26, 26, 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