Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ba8e2781bc80bfd23b7e55e03f8f202ed1e0a19e4df26a64d3fa60fea84faff

Tx prefix hash: d32d737a29f6605f218aef81bdd62b1d7b9f045547135815cb7e82f9ea852e83
Tx public key: 54475ce5072210a312f9fc23fbf1db0a9e103fd23f0fb5e62fc3e396f3f0cdc6
Timestamp: 1580978735 Timestamp [UCT]: 2020-02-06 08:45:35 Age [y:d:h:m:s]: 05:327:19:11:27
Block: 59805 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1384104 RingCT/type: yes/0
Extra: 0154475ce5072210a312f9fc23fbf1db0a9e103fd23f0fb5e62fc3e396f3f0cdc602110000000603d36d11000000000000000000

1 output(s) for total of 388.921057347000 dcy

stealth address amount amount idx
00: 74744e2381d6a7212abe86dd2e26d870950023ad92d077e0cb7bbe6fa0700804 388.921057347000 110319 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": 59815, "vin": [ { "gen": { "height": 59805 } } ], "vout": [ { "amount": 388921057347, "target": { "key": "74744e2381d6a7212abe86dd2e26d870950023ad92d077e0cb7bbe6fa0700804" } } ], "extra": [ 1, 84, 71, 92, 229, 7, 34, 16, 163, 18, 249, 252, 35, 251, 241, 219, 10, 158, 16, 63, 210, 63, 15, 181, 230, 47, 195, 227, 150, 243, 240, 205, 198, 2, 17, 0, 0, 0, 6, 3, 211, 109, 17, 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