Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 60c986ade3aff9434d203d861996a8ee98b1b0f8c1b7673b1c28ce49ad074ef3

Tx prefix hash: 87c7422745d7e861bac297fe05d756ee1b05bc77230468ef0a7c0cc43984bb65
Tx public key: 9cc1fa8e3dcbe8889fafb915f643df7af4d689c1c9d660ab96dc1588748e0919
Timestamp: 1706372698 Timestamp [UCT]: 2024-01-27 16:24:58 Age [y:d:h:m:s]: 01:067:09:14:25
Block: 944557 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309236 RingCT/type: yes/0
Extra: 019cc1fa8e3dcbe8889fafb915f643df7af4d689c1c9d660ab96dc1588748e091902110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 534a06d0d31779bf7c7b078ec909dc62471e8f90c29c556021316cee05c7069c 0.600000000000 1402835 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": 944567, "vin": [ { "gen": { "height": 944557 } } ], "vout": [ { "amount": 600000000, "target": { "key": "534a06d0d31779bf7c7b078ec909dc62471e8f90c29c556021316cee05c7069c" } } ], "extra": [ 1, 156, 193, 250, 142, 61, 203, 232, 136, 159, 175, 185, 21, 246, 67, 223, 122, 244, 214, 137, 193, 201, 214, 96, 171, 150, 220, 21, 136, 116, 142, 9, 25, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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