Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: eaf5200045fb119a413061a897e1db69ed7b7094e6c92c1602a9a4a97836af19

Tx prefix hash: 9a6daf34de11a10315b612d30b128fa0c28ca557d1bca35cbe9f9d7bb14e0d9a
Tx public key: 188acd8af455b830685ae12b9f016f0ca5bcf39be4e187f19d0ba8373756df71
Timestamp: 1726179282 Timestamp [UCT]: 2024-09-12 22:14:42 Age [y:d:h:m:s]: 00:252:05:40:59
Block: 1108793 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 180134 RingCT/type: yes/0
Extra: 01188acd8af455b830685ae12b9f016f0ca5bcf39be4e187f19d0ba8373756df7102110000001ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2ae3ca5d010d9f68185e85d5ba381a743eddc3f814018f3bf762bab83e5fab2 0.600000000000 1586816 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": 1108803, "vin": [ { "gen": { "height": 1108793 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2ae3ca5d010d9f68185e85d5ba381a743eddc3f814018f3bf762bab83e5fab2" } } ], "extra": [ 1, 24, 138, 205, 138, 244, 85, 184, 48, 104, 90, 225, 43, 159, 1, 111, 12, 165, 188, 243, 155, 228, 225, 135, 241, 157, 11, 168, 55, 55, 86, 223, 113, 2, 17, 0, 0, 0, 26, 233, 20, 221, 21, 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