Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b439fec141c009f1131ccf2099b3127039598dd09c2c223778b4e012b72d5797

Tx prefix hash: ecc6c951b2638881dc988106a0ceae23d260e096c01b8931fccf629f1d6f07e6
Tx public key: 3b9c16e8072f8ec0da452c33a449919e623ef23db8ae937bb74f45dac9c826c1
Timestamp: 1724638562 Timestamp [UCT]: 2024-08-26 02:16:02 Age [y:d:h:m:s]: 00:226:19:58:00
Block: 1096006 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161981 RingCT/type: yes/0
Extra: 013b9c16e8072f8ec0da452c33a449919e623ef23db8ae937bb74f45dac9c826c102110000000e91e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ca5f01c2436e10ac0838c70bc4f2093b464ccd509c6b5339e5b9400a8ea04f66 0.600000000000 1571193 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": 1096016, "vin": [ { "gen": { "height": 1096006 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ca5f01c2436e10ac0838c70bc4f2093b464ccd509c6b5339e5b9400a8ea04f66" } } ], "extra": [ 1, 59, 156, 22, 232, 7, 47, 142, 192, 218, 69, 44, 51, 164, 73, 145, 158, 98, 62, 242, 61, 184, 174, 147, 123, 183, 79, 69, 218, 201, 200, 38, 193, 2, 17, 0, 0, 0, 14, 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