Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 667d226f92c8c4d05738e45fd8f79eeb3dd0277858e7df0004b14c0738995bb1

Tx prefix hash: 6f18dde0c1570fb40047b7d9c5374f1d81a33983040eeee6370d9eb792302e20
Tx public key: db92bd7bdc300123a37f8764fdc3c23686d10adf080dba3147bf4110069df3a9
Timestamp: 1660733425 Timestamp [UCT]: 2022-08-17 10:50:25 Age [y:d:h:m:s]: 02:233:14:51:03
Block: 567776 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 688159 RingCT/type: yes/0
Extra: 01db92bd7bdc300123a37f8764fdc3c23686d10adf080dba3147bf4110069df3a902110000000375e3f0e9000000000000000000

1 output(s) for total of 8.067194413000 dcy

stealth address amount amount idx
00: 67ba8a8d7287b8fa0acaaee6c162b55ea9a47fbfb4b28905901f3c669403186c 8.067194413000 1000881 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": 567786, "vin": [ { "gen": { "height": 567776 } } ], "vout": [ { "amount": 8067194413, "target": { "key": "67ba8a8d7287b8fa0acaaee6c162b55ea9a47fbfb4b28905901f3c669403186c" } } ], "extra": [ 1, 219, 146, 189, 123, 220, 48, 1, 35, 163, 127, 135, 100, 253, 195, 194, 54, 134, 209, 10, 223, 8, 13, 186, 49, 71, 191, 65, 16, 6, 157, 243, 169, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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