Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8d9ab245a38545435653b7022e14fcd78d466dfb9e673e2f90e7392690e1f922

Tx prefix hash: 77e5965a30ddc7260eb97bc2d89f5c12d67e0814e8a004f2cc17e7dcaeeca094
Tx public key: d3f01967e63f0dabeefa82fc38e91343297565d2c2c10f4abc4889df296e3550
Timestamp: 1632167776 Timestamp [UCT]: 2021-09-20 19:56:16 Age [y:d:h:m:s]: 03:218:03:37:51
Block: 337734 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 931723 RingCT/type: yes/0
Extra: 01d3f01967e63f0dabeefa82fc38e91343297565d2c2c10f4abc4889df296e355002110000002b3fc41461000000000000000000

1 output(s) for total of 46.660296419000 dcy

stealth address amount amount idx
00: 2106002b6a4c9c2064c45fbe4304aa047b6457698d89f88f052e7812bf7e288f 46.660296419000 695339 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": 337744, "vin": [ { "gen": { "height": 337734 } } ], "vout": [ { "amount": 46660296419, "target": { "key": "2106002b6a4c9c2064c45fbe4304aa047b6457698d89f88f052e7812bf7e288f" } } ], "extra": [ 1, 211, 240, 25, 103, 230, 63, 13, 171, 238, 250, 130, 252, 56, 233, 19, 67, 41, 117, 101, 210, 194, 193, 15, 74, 188, 72, 137, 223, 41, 110, 53, 80, 2, 17, 0, 0, 0, 43, 63, 196, 20, 97, 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