Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4ffdd7684d750b568942abeb6c49f1c063c1a5e388960646f9a637799c5ddff3

Tx prefix hash: c3dcad860f0f4e430efce53c476a2936a56ad421a60630d52f43024215bdd3b4
Tx public key: e522e76031df29596c9e1aef40741b45b3bbc84ea30c6cc71efa0b3f493d2f8e
Timestamp: 1643262035 Timestamp [UCT]: 2022-01-27 05:40:35 Age [y:d:h:m:s]: 02:363:02:54:13
Block: 426122 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 778040 RingCT/type: yes/0
Extra: 01e522e76031df29596c9e1aef40741b45b3bbc84ea30c6cc71efa0b3f493d2f8e021100000001a272b9cb000000000000000000

1 output(s) for total of 23.772849234000 dcy

stealth address amount amount idx
00: a16895b9d0d77446fcd2f55b3f78e6234c07755ac982213346ab5606682f9816 23.772849234000 834913 of 0

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": 426132, "vin": [ { "gen": { "height": 426122 } } ], "vout": [ { "amount": 23772849234, "target": { "key": "a16895b9d0d77446fcd2f55b3f78e6234c07755ac982213346ab5606682f9816" } } ], "extra": [ 1, 229, 34, 231, 96, 49, 223, 41, 89, 108, 158, 26, 239, 64, 116, 27, 69, 179, 187, 200, 78, 163, 12, 108, 199, 30, 250, 11, 63, 73, 61, 47, 142, 2, 17, 0, 0, 0, 1, 162, 114, 185, 203, 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