Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 43e6e64a8b52e61094b9b8f46e086457bc974644f00d5dffd812ef4f1528d525

Tx prefix hash: a5db1e88cd24c23bb274c662055b41caf8167b40ebf4c88b8762d431f34e0985
Tx public key: 8f20f5a5276a3767cf047a964acc8be58b79d5f3572ea5ddaac4d24a78a06cb7
Timestamp: 1707168334 Timestamp [UCT]: 2024-02-05 21:25:34 Age [y:d:h:m:s]: 01:063:16:51:57
Block: 951158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 306593 RingCT/type: yes/0
Extra: 018f20f5a5276a3767cf047a964acc8be58b79d5f3572ea5ddaac4d24a78a06cb70211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 61ed08cd76ee9d62ad40c6dd52ea554d5004a4aea0c0d974a79de403ebadd821 0.600000000000 1409886 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": 951168, "vin": [ { "gen": { "height": 951158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "61ed08cd76ee9d62ad40c6dd52ea554d5004a4aea0c0d974a79de403ebadd821" } } ], "extra": [ 1, 143, 32, 245, 165, 39, 106, 55, 103, 207, 4, 122, 150, 74, 204, 139, 229, 139, 121, 213, 243, 87, 46, 165, 221, 170, 196, 210, 74, 120, 160, 108, 183, 2, 17, 0, 0, 0, 4, 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