Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a55bc59cd4c1e9f40e25c9c9e18396c566221e1ed178b563c2bbbc86cdd65468

Tx prefix hash: 3c72b5454a56d8574ed282e26c2c02abf64ad502c371f655b283dfac62297ee5
Tx public key: c8b5f8b350b62c0e0b6296c171bceffed1d6ceaad24ea258230f573a9b4a5a22
Timestamp: 1626756882 Timestamp [UCT]: 2021-07-20 04:54:42 Age [y:d:h:m:s]: 03:298:02:07:40
Block: 297367 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 984487 RingCT/type: yes/0
Extra: 01c8b5f8b350b62c0e0b6296c171bceffed1d6ceaad24ea258230f573a9b4a5a22021100000011d2fc4d28000000000000000000

1 output(s) for total of 63.489247612000 dcy

stealth address amount amount idx
00: 89e16fa7a801a33b4b0ae4fa88648e57a95ef0459903d966fa1f4d3715f023e5 63.489247612000 622379 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": 297377, "vin": [ { "gen": { "height": 297367 } } ], "vout": [ { "amount": 63489247612, "target": { "key": "89e16fa7a801a33b4b0ae4fa88648e57a95ef0459903d966fa1f4d3715f023e5" } } ], "extra": [ 1, 200, 181, 248, 179, 80, 182, 44, 14, 11, 98, 150, 193, 113, 188, 239, 254, 209, 214, 206, 170, 210, 78, 162, 88, 35, 15, 87, 58, 155, 74, 90, 34, 2, 17, 0, 0, 0, 17, 210, 252, 77, 40, 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