Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 197135676b23415a43fedd99c0bf0bf005bff2a696dd3b0efd8e269acdf86153

Tx prefix hash: 390a10597919bfe80ba4d17ec774695e1f997b756c7d523c944a15b92cc532bf
Tx public key: c8954b9e65aec9a8fb99bf1164e19300ffdd9e522ec16e495a84e084b95f8da0
Timestamp: 1634939364 Timestamp [UCT]: 2021-10-22 21:49:24 Age [y:d:h:m:s]: 03:027:18:59:55
Block: 358379 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 798137 RingCT/type: yes/0
Extra: 01c8954b9e65aec9a8fb99bf1164e19300ffdd9e522ec16e495a84e084b95f8da002110000001df29d7abf000000000000000000

1 output(s) for total of 39.860433186000 dcy

stealth address amount amount idx
00: f5f2dfe2d2dc1fbd4bd610f9338c401e619f2c9cb6bbcf11e9c21c8d9479a4f0 39.860433186000 730264 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": 358389, "vin": [ { "gen": { "height": 358379 } } ], "vout": [ { "amount": 39860433186, "target": { "key": "f5f2dfe2d2dc1fbd4bd610f9338c401e619f2c9cb6bbcf11e9c21c8d9479a4f0" } } ], "extra": [ 1, 200, 149, 75, 158, 101, 174, 201, 168, 251, 153, 191, 17, 100, 225, 147, 0, 255, 221, 158, 82, 46, 193, 110, 73, 90, 132, 224, 132, 185, 95, 141, 160, 2, 17, 0, 0, 0, 29, 242, 157, 122, 191, 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