Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1264b2b3123c6fbb4e863481fea30988864e823b85ee22b71a58975b87c6fcc3

Tx prefix hash: aecdc5483635acf012a1cc61fc62952307a1cda2111fb8422cfd26a29694c0cd
Tx public key: 6450826ed83037fb2309c9b7714f83f614cfffb4c795d4b69d0757725ae2b2e3
Timestamp: 1703583823 Timestamp [UCT]: 2023-12-26 09:43:43 Age [y:d:h:m:s]: 01:062:13:27:44
Block: 921452 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305802 RingCT/type: yes/0
Extra: 016450826ed83037fb2309c9b7714f83f614cfffb4c795d4b69d0757725ae2b2e302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7e876e2794b8e1f5bf4a4dd72cd2985c82ad11c64e81c4c0dbfdddb313123152 0.600000000000 1379140 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": 921462, "vin": [ { "gen": { "height": 921452 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7e876e2794b8e1f5bf4a4dd72cd2985c82ad11c64e81c4c0dbfdddb313123152" } } ], "extra": [ 1, 100, 80, 130, 110, 216, 48, 55, 251, 35, 9, 201, 183, 113, 79, 131, 246, 20, 207, 255, 180, 199, 149, 212, 182, 157, 7, 87, 114, 90, 226, 178, 227, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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