Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a3de1ac12e27a7cf0f3432fe7ccc235eb28b1acefe77dfedc631ba68eba8a0cc

Tx prefix hash: 93769f0e3d4a0c123351147b5eeb07d9715c1e4f6221fecae96dd5d26172ca0e
Tx public key: 3903ac3fa7dd5a61c10b1394ad2053eb18dffd87eb677a802e8f1d5f76d834e1
Timestamp: 1763365032 Timestamp [UCT]: 2025-11-17 07:37:12 Age [y:d:h:m:s]: 00:010:22:15:43
Block: 1413941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 7831 RingCT/type: yes/0
Extra: 013903ac3fa7dd5a61c10b1394ad2053eb18dffd87eb677a802e8f1d5f76d834e102110000000234af31cc000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f8535a2a70df2ae2ce70180f346b0ea095791080fbac78f1eacc04ea193f3f4 0.600000000000 1902422 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": 1413951, "vin": [ { "gen": { "height": 1413941 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f8535a2a70df2ae2ce70180f346b0ea095791080fbac78f1eacc04ea193f3f4" } } ], "extra": [ 1, 57, 3, 172, 63, 167, 221, 90, 97, 193, 11, 19, 148, 173, 32, 83, 235, 24, 223, 253, 135, 235, 103, 122, 128, 46, 143, 29, 95, 118, 216, 52, 225, 2, 17, 0, 0, 0, 2, 52, 175, 49, 204, 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