Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1a6d9a5dfc041778917df6a8603f24658845530046e55ad2edf2c4b1fb39ab73

Tx prefix hash: bcbc63acb9f2c606db4ff325dceee03bb5840ecf72665367e1541c4190177159
Tx public key: 2a3b5d2d70c7b9ce647665db50f981c56d454e765fca68d8404ece23fb5b6eb5
Timestamp: 1727790100 Timestamp [UCT]: 2024-10-01 13:41:40 Age [y:d:h:m:s]: 00:113:09:13:06
Block: 1122142 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 81023 RingCT/type: yes/0
Extra: 012a3b5d2d70c7b9ce647665db50f981c56d454e765fca68d8404ece23fb5b6eb5021100000005e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8e75a2a4877dc608a0a29d7f05626453455f105138548ed4888762f1afd5dfd 0.600000000000 1604533 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": 1122152, "vin": [ { "gen": { "height": 1122142 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8e75a2a4877dc608a0a29d7f05626453455f105138548ed4888762f1afd5dfd" } } ], "extra": [ 1, 42, 59, 93, 45, 112, 199, 185, 206, 100, 118, 101, 219, 80, 249, 129, 197, 109, 69, 78, 118, 95, 202, 104, 216, 64, 78, 206, 35, 251, 91, 110, 181, 2, 17, 0, 0, 0, 5, 233, 20, 221, 21, 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