Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c1bfaaa2854571c58ccb718314b671ce3593c1688d8df7e5306d6da571ba3949

Tx prefix hash: 0d6ac09a08a9ccc77ee7fbd149eaf5ed0e0fa6d6459767c490fa712070d5e3d0
Tx public key: fc8d66d0eb48b91e055fac595733f717a77a29cdbb61812b2d6f8a7720bdb23e
Timestamp: 1718068574 Timestamp [UCT]: 2024-06-11 01:16:14 Age [y:d:h:m:s]: 00:288:07:51:43
Block: 1041552 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 206024 RingCT/type: yes/0
Extra: 01fc8d66d0eb48b91e055fac595733f717a77a29cdbb61812b2d6f8a7720bdb23e0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 92290c9f48d450294f06291eb270a98dac372910ca302e508833a34ec1974aae 0.600000000000 1510253 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": 1041562, "vin": [ { "gen": { "height": 1041552 } } ], "vout": [ { "amount": 600000000, "target": { "key": "92290c9f48d450294f06291eb270a98dac372910ca302e508833a34ec1974aae" } } ], "extra": [ 1, 252, 141, 102, 208, 235, 72, 185, 30, 5, 95, 172, 89, 87, 51, 247, 23, 167, 122, 41, 205, 187, 97, 129, 43, 45, 111, 138, 119, 32, 189, 178, 62, 2, 17, 0, 0, 0, 1, 122, 156, 244, 199, 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