Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 833076b1dadd16c43f50fea1292c08b711b0d9bc044b8834e8f9c5fc52bba8d4

Tx prefix hash: db284d87e08145d9b7034960ab6547a73fee50cb703363236520492165078d7b
Tx public key: 17d8d96a8d50c475d84c6f951930e0ebd532bd25d0b261be05d9f2c24b389306
Timestamp: 1727719649 Timestamp [UCT]: 2024-09-30 18:07:29 Age [y:d:h:m:s]: 01:038:17:24:31
Block: 1121558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 286054 RingCT/type: yes/0
Extra: 0117d8d96a8d50c475d84c6f951930e0ebd532bd25d0b261be05d9f2c24b38930602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 493c8d5ce9884f17eee5b3246effb7e9f199859262166eec7685caca00db151c 0.600000000000 1603847 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": 1121568, "vin": [ { "gen": { "height": 1121558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "493c8d5ce9884f17eee5b3246effb7e9f199859262166eec7685caca00db151c" } } ], "extra": [ 1, 23, 216, 217, 106, 141, 80, 196, 117, 216, 76, 111, 149, 25, 48, 224, 235, 213, 50, 189, 37, 208, 178, 97, 190, 5, 217, 242, 194, 75, 56, 147, 6, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 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