Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2a60083876c6847b6875bd7a530291d1ec09a797e55aa43cf8cf15cdaafb0fdf

Tx prefix hash: d4f9cb0645a56315c4a70daa63732463e9ee87d82815c0c762d80f3b766032ab
Tx public key: aa1585fa7078480e930d1c346b187121325becd44bf3cf237e2c354f30796744
Timestamp: 1724508443 Timestamp [UCT]: 2024-08-24 14:07:23 Age [y:d:h:m:s]: 00:092:04:52:13
Block: 1094960 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 65916 RingCT/type: yes/0
Extra: 01aa1585fa7078480e930d1c346b187121325becd44bf3cf237e2c354f3079674402110000000be337358e000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8b2cf9a3332baaab46b674d2d8af9a4fe07b3ea432bd06543c539e286dd8c94c 0.600000000000 1570083 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": 1094970, "vin": [ { "gen": { "height": 1094960 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8b2cf9a3332baaab46b674d2d8af9a4fe07b3ea432bd06543c539e286dd8c94c" } } ], "extra": [ 1, 170, 21, 133, 250, 112, 120, 72, 14, 147, 13, 28, 52, 107, 24, 113, 33, 50, 91, 236, 212, 75, 243, 207, 35, 126, 44, 53, 79, 48, 121, 103, 68, 2, 17, 0, 0, 0, 11, 227, 55, 53, 142, 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