Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cf8b6fbdea6a000d892365b66b172130e9c9f16656cfd31eaf3a270af77a97e7

Tx prefix hash: 0320c0975e44d54819a7c12f2d5adeb9dee98896de97d9819509ab2e34fc1909
Tx public key: 83e8bf59314f552bd8e461ace968951ebdb977874d85fdddb1cdfdc093f726b4
Timestamp: 1581249767 Timestamp [UCT]: 2020-02-09 12:02:47 Age [y:d:h:m:s]: 04:297:14:29:19
Block: 61345 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1104776 RingCT/type: yes/0
Extra: 0183e8bf59314f552bd8e461ace968951ebdb977874d85fdddb1cdfdc093f726b40211000000a256c366d3000000000000000000

1 output(s) for total of 384.371915325000 dcy

stealth address amount amount idx
00: 9f01441d24fc082cf0c56d7da04143cfd174a21e4d4716f6bb791c5ad1e43242 384.371915325000 113039 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": 61355, "vin": [ { "gen": { "height": 61345 } } ], "vout": [ { "amount": 384371915325, "target": { "key": "9f01441d24fc082cf0c56d7da04143cfd174a21e4d4716f6bb791c5ad1e43242" } } ], "extra": [ 1, 131, 232, 191, 89, 49, 79, 85, 43, 216, 228, 97, 172, 233, 104, 149, 30, 189, 185, 119, 135, 77, 133, 253, 221, 177, 205, 253, 192, 147, 247, 38, 180, 2, 17, 0, 0, 0, 162, 86, 195, 102, 211, 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