Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec768b3ab8f77016f3639ff17c5e0d1f1b7edf2aefa77b25b5c5f57b6fd32a0

Tx prefix hash: d5edf20979ebb776afead9a5763e2b48183b6e6a232ce9031c58d5fe6768e21e
Tx public key: e51612b07ddf86a16e19db992583195671ef233f47c8b97f250afc86ce323802
Timestamp: 1621555079 Timestamp [UCT]: 2021-05-20 23:57:59 Age [y:d:h:m:s]: 03:230:00:01:02
Block: 264300 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 926069 RingCT/type: yes/0
Extra: 01e51612b07ddf86a16e19db992583195671ef233f47c8b97f250afc86ce32380202110000001923fdb90b000000000000000000

1 output(s) for total of 81.709475044000 dcy

stealth address amount amount idx
00: c8e12b2fa03a424cb6d30b0c6e9efaa195f21899b5c6010f1f3ed3193d851ca6 81.709475044000 555792 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": 264310, "vin": [ { "gen": { "height": 264300 } } ], "vout": [ { "amount": 81709475044, "target": { "key": "c8e12b2fa03a424cb6d30b0c6e9efaa195f21899b5c6010f1f3ed3193d851ca6" } } ], "extra": [ 1, 229, 22, 18, 176, 125, 223, 134, 161, 110, 25, 219, 153, 37, 131, 25, 86, 113, 239, 35, 63, 71, 200, 185, 127, 37, 10, 252, 134, 206, 50, 56, 2, 2, 17, 0, 0, 0, 25, 35, 253, 185, 11, 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