Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94636acdc8611e9e66614dc4cb479cb10fb4e8cb9fdefe4e1b59b4bc726467d7

Tx prefix hash: 569b70507c4bec7084e1aaf19c20b293d5af8de3ff5e25ffef432cbfc102ec98
Tx public key: c8d8fea457e3f2cb6ecf4784424c3925eee87b79334dff007fc85056aac76779
Timestamp: 1737393494 Timestamp [UCT]: 2025-01-20 17:18:14 Age [y:d:h:m:s]: 00:304:16:21:44
Block: 1201558 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 215302 RingCT/type: yes/0
Extra: 01c8d8fea457e3f2cb6ecf4784424c3925eee87b79334dff007fc85056aac767790211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eabfe2ee93ac3cc2fae0eb9ed73a92c577503bebe40a9d295bb21eca0c6bc0a5 0.600000000000 1688211 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": 1201568, "vin": [ { "gen": { "height": 1201558 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eabfe2ee93ac3cc2fae0eb9ed73a92c577503bebe40a9d295bb21eca0c6bc0a5" } } ], "extra": [ 1, 200, 216, 254, 164, 87, 227, 242, 203, 110, 207, 71, 132, 66, 76, 57, 37, 238, 232, 123, 121, 51, 77, 255, 0, 127, 200, 80, 86, 170, 199, 103, 121, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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