Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b63df77084f38fd50468a2d24d8ee3c0eacc985139e97e970e86ced931c95e7e

Tx prefix hash: 9a627cbdc8e68558fff924f3d2674e89f494904eca6cc1e0960a405a7f3c3178
Tx public key: 0febbb22b923104afe2fe1c9ce2fe7ff45db8aec5e2cf0b1ffd802ac32ff3c9f
Timestamp: 1718256895 Timestamp [UCT]: 2024-06-13 05:34:55 Age [y:d:h:m:s]: 00:322:10:01:48
Block: 1043104 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 230433 RingCT/type: yes/0
Extra: 010febbb22b923104afe2fe1c9ce2fe7ff45db8aec5e2cf0b1ffd802ac32ff3c9f0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b9bbf12b62a0760fe249a9c145d9c4e7046d350ae62c944ee9d4a088443914be 0.600000000000 1512177 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": 1043114, "vin": [ { "gen": { "height": 1043104 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b9bbf12b62a0760fe249a9c145d9c4e7046d350ae62c944ee9d4a088443914be" } } ], "extra": [ 1, 15, 235, 187, 34, 185, 35, 16, 74, 254, 47, 225, 201, 206, 47, 231, 255, 69, 219, 138, 236, 94, 44, 240, 177, 255, 216, 2, 172, 50, 255, 60, 159, 2, 17, 0, 0, 0, 5, 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