Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08cbe5439e555b70880db3e0f32d549222cc18f8591741967b1bf0eb55e26b64

Tx prefix hash: be8923f6df4dfd36004071ffe269de9e815879d9a5c3d1d48fb0f3a210600166
Tx public key: f4c9563555e0af63ec0c6669ac43e820c6c378de71b2e1bc796e4e1fcfd3e3ee
Timestamp: 1592954043 Timestamp [UCT]: 2020-06-23 23:14:03 Age [y:d:h:m:s]: 04:250:20:49:26
Block: 110356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118956 RingCT/type: yes/0
Extra: 01f4c9563555e0af63ec0c6669ac43e820c6c378de71b2e1bc796e4e1fcfd3e3ee0211000000128a2ee0d9000000000000000000

1 output(s) for total of 264.460309606000 dcy

stealth address amount amount idx
00: d42be1b49317ec5414c85b8cf43dfac7c8e3b8444daa4ffb717a1af7d8cc1492 264.460309606000 191164 of 0

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": 110366, "vin": [ { "gen": { "height": 110356 } } ], "vout": [ { "amount": 264460309606, "target": { "key": "d42be1b49317ec5414c85b8cf43dfac7c8e3b8444daa4ffb717a1af7d8cc1492" } } ], "extra": [ 1, 244, 201, 86, 53, 85, 224, 175, 99, 236, 12, 102, 105, 172, 67, 232, 32, 198, 195, 120, 222, 113, 178, 225, 188, 121, 110, 78, 31, 207, 211, 227, 238, 2, 17, 0, 0, 0, 18, 138, 46, 224, 217, 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