Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afe35c29b844b369b48a3d5348a03588de22115bfd8f3744acbe93bcca6b9442

Tx prefix hash: ff05562902e85f0dbbd62db6279bb49e940fb44969cf2ae6fe09dfb4a453860f
Tx public key: 154a178d0d5e858c4df83f3c248092832915018edf9e39d3b132fe69eeefeb0b
Timestamp: 1726476856 Timestamp [UCT]: 2024-09-16 08:54:16 Age [y:d:h:m:s]: 00:160:01:58:23
Block: 1111259 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 114188 RingCT/type: yes/0
Extra: 01154a178d0d5e858c4df83f3c248092832915018edf9e39d3b132fe69eeefeb0b021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1e2faa3c2a1a8411b29d8b826fc3acf6dc2be215e7ac0cb0bec804b22a7813c2 0.600000000000 1590154 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": 1111269, "vin": [ { "gen": { "height": 1111259 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1e2faa3c2a1a8411b29d8b826fc3acf6dc2be215e7ac0cb0bec804b22a7813c2" } } ], "extra": [ 1, 21, 74, 23, 141, 13, 94, 133, 140, 77, 248, 63, 60, 36, 128, 146, 131, 41, 21, 1, 142, 223, 158, 57, 211, 177, 50, 254, 105, 238, 239, 235, 11, 2, 17, 0, 0, 0, 2, 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