Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c6550de0081745eae34622d25ab53f4e1990e2b4357780ac4d8b72cc45221bc

Tx prefix hash: 875165736a51b729ac883ad17254c816f83ca7b82daf8b4aed3b3619d2d66d58
Tx public key: f5a9b127010e0360d964916f26e935a969359c8b53b1c85a8247d3d183300bb7
Timestamp: 1728865480 Timestamp [UCT]: 2024-10-14 00:24:40 Age [y:d:h:m:s]: 00:186:14:33:12
Block: 1131055 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133163 RingCT/type: yes/0
Extra: 01f5a9b127010e0360d964916f26e935a969359c8b53b1c85a8247d3d183300bb7021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7c4b243455a0a46f32a0b730415f4f7f8af82f936308545b2f8a84932b6a5d00 0.600000000000 1613936 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": 1131065, "vin": [ { "gen": { "height": 1131055 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7c4b243455a0a46f32a0b730415f4f7f8af82f936308545b2f8a84932b6a5d00" } } ], "extra": [ 1, 245, 169, 177, 39, 1, 14, 3, 96, 217, 100, 145, 111, 38, 233, 53, 169, 105, 53, 156, 139, 83, 177, 200, 90, 130, 71, 211, 209, 131, 48, 11, 183, 2, 17, 0, 0, 0, 1, 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