Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3263871b08c3db81a0466020a201e6e7514c75405bc2111765276da31f4e084c

Tx prefix hash: a8c7182caf32ec1fe1324229b1446eb39053441a35ef0f55b6e5e50a782fccdd
Tx public key: e5522d6a1410faf9ee2b1c6f70876d17769f3f8159fa7b32860d64c514a0a233
Timestamp: 1726674064 Timestamp [UCT]: 2024-09-18 15:41:04 Age [y:d:h:m:s]: 01:063:02:12:37
Block: 1112878 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 303520 RingCT/type: yes/0
Extra: 01e5522d6a1410faf9ee2b1c6f70876d17769f3f8159fa7b32860d64c514a0a233021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1be20e6532fe737344b0b50df097531abc8c7a5411a3b5b501748954a3620e77 0.600000000000 1592355 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": 1112888, "vin": [ { "gen": { "height": 1112878 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1be20e6532fe737344b0b50df097531abc8c7a5411a3b5b501748954a3620e77" } } ], "extra": [ 1, 229, 82, 45, 106, 20, 16, 250, 249, 238, 43, 28, 111, 112, 135, 109, 23, 118, 159, 63, 129, 89, 250, 123, 50, 134, 13, 100, 197, 20, 160, 162, 51, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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