Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2f0bc0641f3d1d516f4665d1333c95d14590e689ffd1c4dd937cb464110c7e3f

Tx prefix hash: a65883e0d6977e85458b76d26354c5ca5a929e339214eeea0ed033838da3a5f4
Tx public key: 91e67504e0f4cad036db08eec1037d7723d80bf6c359bf1c6dc9aa19882a8622
Timestamp: 1724604711 Timestamp [UCT]: 2024-08-25 16:51:51 Age [y:d:h:m:s]: 01:077:00:26:40
Block: 1095736 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 313485 RingCT/type: yes/0
Extra: 0191e67504e0f4cad036db08eec1037d7723d80bf6c359bf1c6dc9aa19882a862202110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ce426493040f6dd177a443b0ac2bd912c96d49ce0907e1e4362caccfd5a3103c 0.600000000000 1570917 of 15

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": 1095746, "vin": [ { "gen": { "height": 1095736 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ce426493040f6dd177a443b0ac2bd912c96d49ce0907e1e4362caccfd5a3103c" } } ], "extra": [ 1, 145, 230, 117, 4, 224, 244, 202, 208, 54, 219, 8, 238, 193, 3, 125, 119, 35, 216, 11, 246, 195, 89, 191, 28, 109, 201, 170, 25, 136, 42, 134, 34, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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