Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 324f54361e037320d2fd2cf166ddd8a29a8d63ea912913730f0246d62cb2305b

Tx prefix hash: d5575d4b9a7b3f05264ec51ea3151e237f8568eea67d2b032a95ab7e2c214987
Tx public key: 7926b1f3e3eb0cd85ff5de662aba065852adef12597fb46b9703c3fffa4fab81
Timestamp: 1581948170 Timestamp [UCT]: 2020-02-17 14:02:50 Age [y:d:h:m:s]: 04:263:00:35:55
Block: 66780 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1080365 RingCT/type: yes/0
Extra: 017926b1f3e3eb0cd85ff5de662aba065852adef12597fb46b9703c3fffa4fab810211000000010aca7173000000000000000000

1 output(s) for total of 368.749081056000 dcy

stealth address amount amount idx
00: 419cc6b966e6b7e9087dc8353c725dc12fff7fe02972bd07215b88e79ff8b583 368.749081056000 122976 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": 66790, "vin": [ { "gen": { "height": 66780 } } ], "vout": [ { "amount": 368749081056, "target": { "key": "419cc6b966e6b7e9087dc8353c725dc12fff7fe02972bd07215b88e79ff8b583" } } ], "extra": [ 1, 121, 38, 177, 243, 227, 235, 12, 216, 95, 245, 222, 102, 42, 186, 6, 88, 82, 173, 239, 18, 89, 127, 180, 107, 151, 3, 195, 255, 250, 79, 171, 129, 2, 17, 0, 0, 0, 1, 10, 202, 113, 115, 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