Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0024932c215a8fa82fd915ba4b319204c5f03905a03bdc0b6c4ac7fc85b15a4b

Tx prefix hash: 41443270119f885f1a4c0b63f0b600f4f97ad4a07033cf467d0b4c5c3bcf6b38
Tx public key: ea0a4adf11277096d9238e134c7082be82121f70b42046013fdd88eb4dd9d983
Timestamp: 1707038739 Timestamp [UCT]: 2024-02-04 09:25:39 Age [y:d:h:m:s]: 01:281:16:19:27
Block: 950091 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 460096 RingCT/type: yes/0
Extra: 01ea0a4adf11277096d9238e134c7082be82121f70b42046013fdd88eb4dd9d98302110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7a4e2be74b6d06a936cdac9d66905cd98e9c6690396ac5ab5126de1b3cb092b8 0.600000000000 1408651 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": 950101, "vin": [ { "gen": { "height": 950091 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7a4e2be74b6d06a936cdac9d66905cd98e9c6690396ac5ab5126de1b3cb092b8" } } ], "extra": [ 1, 234, 10, 74, 223, 17, 39, 112, 150, 217, 35, 142, 19, 76, 112, 130, 190, 130, 18, 31, 112, 180, 32, 70, 1, 63, 221, 136, 235, 77, 217, 217, 131, 2, 17, 0, 0, 0, 2, 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