Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b1ced10395d943f8a830ea35c814f2ddf4b55dee19bdb446709eec5b4954b47

Tx prefix hash: 2832151f316e056495e8189690589584ee94b2771eb03d1abf6c028d6c95a2d1
Tx public key: fc4925bf16cb20e9a720b5f153df1c5d14e22502e0e08624c269bba0968f4b76
Timestamp: 1625127464 Timestamp [UCT]: 2021-07-01 08:17:44 Age [y:d:h:m:s]: 03:141:12:28:15
Block: 286394 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 870235 RingCT/type: yes/0
Extra: 01fc4925bf16cb20e9a720b5f153df1c5d14e22502e0e08624c269bba0968f4b760211000001c93525d189000000000000000000

1 output(s) for total of 69.034446886000 dcy

stealth address amount amount idx
00: 38ea99471adeb24aee26d102fcfdc1fc5866399e08c97960cb48290e9830f734 69.034446886000 599745 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": 286404, "vin": [ { "gen": { "height": 286394 } } ], "vout": [ { "amount": 69034446886, "target": { "key": "38ea99471adeb24aee26d102fcfdc1fc5866399e08c97960cb48290e9830f734" } } ], "extra": [ 1, 252, 73, 37, 191, 22, 203, 32, 233, 167, 32, 181, 241, 83, 223, 28, 93, 20, 226, 37, 2, 224, 224, 134, 36, 194, 105, 187, 160, 150, 143, 75, 118, 2, 17, 0, 0, 1, 201, 53, 37, 209, 137, 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