Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d2578686eeaf1d5f7f82c9326277b63dada923e1769aab3916c45e80df00e5d

Tx prefix hash: 9522d4e2b3b246566be8a5cca7dd446269cdbef42cb35ee8478cd70a0370d3e2
Tx public key: 68da5f32d393770fd609ddc047ac2a736cebd77e04ce2a573cadc2b9915aa26a
Timestamp: 1578322859 Timestamp [UCT]: 2020-01-06 15:00:59 Age [y:d:h:m:s]: 05:058:04:54:05
Block: 39751 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1191711 RingCT/type: yes/0
Extra: 0168da5f32d393770fd609ddc047ac2a736cebd77e04ce2a573cadc2b9915aa26a02110000009517786bcf000000000000000000

1 output(s) for total of 453.199355497000 dcy

stealth address amount amount idx
00: 5e6d12fd8db52d28a928238845d46d85dcc175f06dc9dc84e0383a1d714c4703 453.199355497000 69017 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": 39761, "vin": [ { "gen": { "height": 39751 } } ], "vout": [ { "amount": 453199355497, "target": { "key": "5e6d12fd8db52d28a928238845d46d85dcc175f06dc9dc84e0383a1d714c4703" } } ], "extra": [ 1, 104, 218, 95, 50, 211, 147, 119, 15, 214, 9, 221, 192, 71, 172, 42, 115, 108, 235, 215, 126, 4, 206, 42, 87, 60, 173, 194, 185, 145, 90, 162, 106, 2, 17, 0, 0, 0, 149, 23, 120, 107, 207, 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