Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 83e97c2f83d01ee6acce6d2a56ebe0d311916569c14b67475c19b6707303601b

Tx prefix hash: 624abf5a733a297744c34a7f159132815b6224ce2a0ceeb5c59669d839c5aaa8
Tx public key: c79618ddcaa5729d468ce91cf751ec3aedcf3b4ed3b9d52916c9082fdc2c730a
Timestamp: 1718870630 Timestamp [UCT]: 2024-06-20 08:03:50 Age [y:d:h:m:s]: 01:145:11:56:30
Block: 1048193 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362547 RingCT/type: yes/0
Extra: 01c79618ddcaa5729d468ce91cf751ec3aedcf3b4ed3b9d52916c9082fdc2c730a0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e06def61b761287d330112914b3f94b1aa0e2b679456b33067fc176fc999ad2 0.600000000000 1518216 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": 1048203, "vin": [ { "gen": { "height": 1048193 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e06def61b761287d330112914b3f94b1aa0e2b679456b33067fc176fc999ad2" } } ], "extra": [ 1, 199, 150, 24, 221, 202, 165, 114, 157, 70, 140, 233, 28, 247, 81, 236, 58, 237, 207, 59, 78, 211, 185, 213, 41, 22, 201, 8, 47, 220, 44, 115, 10, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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