Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b5a5cf941ca249cb21929b7e11f26ae8961dedf116cb1bf8453771e4f676e28

Tx prefix hash: 82ea641decdc019e112127997d43c6b224b9b6b00c13d2000cb234bc083a4bff
Tx public key: 257fe60220f64c1ed54c3bcb3aab7c9b8744571dbda0f9d9295cd5ac4826b14a
Timestamp: 1712073134 Timestamp [UCT]: 2024-04-02 15:52:14 Age [y:d:h:m:s]: 01:243:19:07:43
Block: 991806 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 432988 RingCT/type: yes/0
Extra: 01257fe60220f64c1ed54c3bcb3aab7c9b8744571dbda0f9d9295cd5ac4826b14a0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c42141fb1b73ba87f959900db1b6786c3836b91c68bf65c1f5414cc502ac3ba3 0.600000000000 1452142 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": 991816, "vin": [ { "gen": { "height": 991806 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c42141fb1b73ba87f959900db1b6786c3836b91c68bf65c1f5414cc502ac3ba3" } } ], "extra": [ 1, 37, 127, 230, 2, 32, 246, 76, 30, 213, 76, 59, 203, 58, 171, 124, 155, 135, 68, 87, 29, 189, 160, 249, 217, 41, 92, 213, 172, 72, 38, 177, 74, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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