Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2c1f7a58c0aa42a66f9aa300db4f01554379503043a42012e1ee06419d89b774

Tx prefix hash: c8838cc2e667afe83f76b0c21cea3070d09f7118014eedf6a8fb067f17fa9f31
Tx public key: 2444e9c7ded2d3f39d3e297e44ffd15a54b6faa9cede0769d519f195a5b87423
Timestamp: 1721717250 Timestamp [UCT]: 2024-07-23 06:47:30 Age [y:d:h:m:s]: 00:123:22:32:11
Block: 1071784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88687 RingCT/type: yes/0
Extra: 012444e9c7ded2d3f39d3e297e44ffd15a54b6faa9cede0769d519f195a5b8742302110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5e7256caec710f8fb442187449ccafc5453a404d17e3f2d08278a48d17c938bb 0.600000000000 1544139 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": 1071794, "vin": [ { "gen": { "height": 1071784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5e7256caec710f8fb442187449ccafc5453a404d17e3f2d08278a48d17c938bb" } } ], "extra": [ 1, 36, 68, 233, 199, 222, 210, 211, 243, 157, 62, 41, 126, 68, 255, 209, 90, 84, 182, 250, 169, 206, 222, 7, 105, 213, 25, 241, 149, 165, 184, 116, 35, 2, 17, 0, 0, 0, 7, 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