Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b863a71fc01f17a52c7976e0cd1fe15260fa32b6fa344b19bdaa127c63078e46

Tx prefix hash: aa6c087986264b43260961382c5b7b5bf1411bc804b28a69ba403819ccecd5ee
Tx public key: 0641257e4702fbe84b6adb2eba7a9c63b5f76d8c9342d0bb5319675dfee6bfca
Timestamp: 1574571630 Timestamp [UCT]: 2019-11-24 05:00:30 Age [y:d:h:m:s]: 05:342:23:39:49
Block: 16190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0986 kB
Tx version: 2 No of confirmations: 1385512 RingCT/type: yes/0
Extra: 010641257e4702fbe84b6adb2eba7a9c63b5f76d8c9342d0bb5319675dfee6bfca021100000006f95225a5000000000000000000

1 output(s) for total of 542.446225533000 dcy

stealth address amount amount idx
00: 356423059a38bb64cda8b354129341705f828e8ccbd83c98c5872a346a80fd33 542.446225533000 22442 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": 16200, "vin": [ { "gen": { "height": 16190 } } ], "vout": [ { "amount": 542446225533, "target": { "key": "356423059a38bb64cda8b354129341705f828e8ccbd83c98c5872a346a80fd33" } } ], "extra": [ 1, 6, 65, 37, 126, 71, 2, 251, 232, 75, 106, 219, 46, 186, 122, 156, 99, 181, 247, 109, 140, 147, 66, 208, 187, 83, 25, 103, 93, 254, 230, 191, 202, 2, 17, 0, 0, 0, 6, 249, 82, 37, 165, 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