Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c96bc4d520f88e6054d505e09cc52ab2b2a6df047476f3d60afe330194cb16c5

Tx prefix hash: 4ac25130f0844f9fd6082079c235ef1dead2f1aef4cb43e9563f6a1c763666fe
Tx public key: 3300cc6a5c6c974bce15080b2f65aa76a213c9778922a9e018af35353dadd82c
Timestamp: 1721189231 Timestamp [UCT]: 2024-07-17 04:07:11 Age [y:d:h:m:s]: 01:110:06:18:03
Block: 1067430 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337291 RingCT/type: yes/0
Extra: 013300cc6a5c6c974bce15080b2f65aa76a213c9778922a9e018af35353dadd82c02110000001091e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c5726233f59444e6c3b2a74b2da27e5068afa01c8f836c738b9055f7033e92a 0.600000000000 1538239 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": 1067440, "vin": [ { "gen": { "height": 1067430 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c5726233f59444e6c3b2a74b2da27e5068afa01c8f836c738b9055f7033e92a" } } ], "extra": [ 1, 51, 0, 204, 106, 92, 108, 151, 75, 206, 21, 8, 11, 47, 101, 170, 118, 162, 19, 201, 119, 137, 34, 169, 224, 24, 175, 53, 53, 61, 173, 216, 44, 2, 17, 0, 0, 0, 16, 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