Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a0cda7d96b306979390a369523a8e2812d288df984675b4dbf5b7a41f3792a03

Tx prefix hash: c0ede3b65fee3d5f977ec7e77a45b0840c9f42f13cea381142fb7a5a1a274971
Tx public key: 1e6f6917780febf4e6ddab6e9ec8b4d740afef9732384abae8b8b29c681eb971
Timestamp: 1704658702 Timestamp [UCT]: 2024-01-07 20:18:22 Age [y:d:h:m:s]: 01:112:06:14:24
Block: 930346 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341378 RingCT/type: yes/0
Extra: 011e6f6917780febf4e6ddab6e9ec8b4d740afef9732384abae8b8b29c681eb97102110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 808ba5a7093730612996af3ba84e6480f20ccb90e3f4d0b520a760861b1d4987 0.600000000000 1388228 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": 930356, "vin": [ { "gen": { "height": 930346 } } ], "vout": [ { "amount": 600000000, "target": { "key": "808ba5a7093730612996af3ba84e6480f20ccb90e3f4d0b520a760861b1d4987" } } ], "extra": [ 1, 30, 111, 105, 23, 120, 15, 235, 244, 230, 221, 171, 110, 158, 200, 180, 215, 64, 175, 239, 151, 50, 56, 74, 186, 232, 184, 178, 156, 104, 30, 185, 113, 2, 17, 0, 0, 0, 1, 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