Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c0e2ef2d8fe1edf80373b517c401fb0b61cbdc6684e17760020e082a59c537b0

Tx prefix hash: d8a7ec62dfe2bc06d36d59aa425753e7bd5516500c903c7d7d5b4f2b3a9d9e46
Tx public key: 680b04baf0cd8bf80fe947a5e2c658d036d4d230efad5e871a4c62fa201e4e0c
Timestamp: 1734450443 Timestamp [UCT]: 2024-12-17 15:47:23 Age [y:d:h:m:s]: 00:174:16:19:50
Block: 1177268 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 124661 RingCT/type: yes/0
Extra: 01680b04baf0cd8bf80fe947a5e2c658d036d4d230efad5e871a4c62fa201e4e0c0211000000081f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8159ba1dea25841724701b65334d84a84eea7e8a2824e13c5f294d9aaaadb168 0.600000000000 1663635 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": 1177278, "vin": [ { "gen": { "height": 1177268 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8159ba1dea25841724701b65334d84a84eea7e8a2824e13c5f294d9aaaadb168" } } ], "extra": [ 1, 104, 11, 4, 186, 240, 205, 139, 248, 15, 233, 71, 165, 226, 198, 88, 208, 54, 212, 210, 48, 239, 173, 94, 135, 26, 76, 98, 250, 32, 30, 78, 12, 2, 17, 0, 0, 0, 8, 31, 10, 83, 235, 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