Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c02f2f02ffc8f26d87af78b02c4e85cb772a79c2d72caa4282915945ebcc80d0

Tx prefix hash: a3fab3aa52e4f5f026d567a7ed8ae76db626e4733b54af09537384665fc82a27
Tx public key: 496fef566b8852437e62177a99249b2a8e61dd6bcd8bffddb4e288cb3ae168ed
Timestamp: 1736829407 Timestamp [UCT]: 2025-01-14 04:36:47 Age [y:d:h:m:s]: 00:342:03:19:55
Block: 1196942 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 242069 RingCT/type: yes/0
Extra: 01496fef566b8852437e62177a99249b2a8e61dd6bcd8bffddb4e288cb3ae168ed0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c5d1fe84750534968cf562528c3ba2227d9f7da25d327c968a0be084f771a1be 0.600000000000 1683547 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": 1196952, "vin": [ { "gen": { "height": 1196942 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c5d1fe84750534968cf562528c3ba2227d9f7da25d327c968a0be084f771a1be" } } ], "extra": [ 1, 73, 111, 239, 86, 107, 136, 82, 67, 126, 98, 23, 122, 153, 36, 155, 42, 142, 97, 221, 107, 205, 139, 255, 221, 180, 226, 136, 203, 58, 225, 104, 237, 2, 17, 0, 0, 0, 2, 31, 10, 83, 235, 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