Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 70a26f3707e98f144dc1f82df126821812f542e860a085be1ccd8895789ee617

Tx prefix hash: 0da592ec3e656689a4209efde8899eaab3334a6e5bed681220941c36b4aa95ef
Tx public key: 2afd3774a13c9d8d0e3c3df19846cff6c5fbbbacd5d2d8506efdc8ec1f32cb84
Timestamp: 1581824534 Timestamp [UCT]: 2020-02-16 03:42:14 Age [y:d:h:m:s]: 04:284:20:39:38
Block: 66048 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1095705 RingCT/type: yes/0
Extra: 012afd3774a13c9d8d0e3c3df19846cff6c5fbbbacd5d2d8506efdc8ec1f32cb840211000000017adf42d3000000000000000000

1 output(s) for total of 370.814209331000 dcy

stealth address amount amount idx
00: 854b8a95efa57a1c36791b3bb8679b49a3ea6b7b495b3f5d6a30ddb8caa8e23d 370.814209331000 121693 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": 66058, "vin": [ { "gen": { "height": 66048 } } ], "vout": [ { "amount": 370814209331, "target": { "key": "854b8a95efa57a1c36791b3bb8679b49a3ea6b7b495b3f5d6a30ddb8caa8e23d" } } ], "extra": [ 1, 42, 253, 55, 116, 161, 60, 157, 141, 14, 60, 61, 241, 152, 70, 207, 246, 197, 251, 187, 172, 213, 210, 216, 80, 110, 253, 200, 236, 31, 50, 203, 132, 2, 17, 0, 0, 0, 1, 122, 223, 66, 211, 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