Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 81565beb15cc23168c609b183c67148f9ffceca5c0f9de8e176d1114ebfb3189

Tx prefix hash: 97061237f554ec51566e0ff472236d95e9f63cbd389ed9670dd351c03aa0b20e
Tx public key: 78c5bf548f5092c18383eab790278872c0ab5c7f705e5fa61bb4e928b34cd6a5
Timestamp: 1581704642 Timestamp [UCT]: 2020-02-14 18:24:02 Age [y:d:h:m:s]: 04:279:15:56:28
Block: 65306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1091739 RingCT/type: yes/0
Extra: 0178c5bf548f5092c18383eab790278872c0ab5c7f705e5fa61bb4e928b34cd6a50211000000057adf42d3000000000000000000

1 output(s) for total of 372.919353584000 dcy

stealth address amount amount idx
00: 50c327f4c3b876e2b1187bad89b566e040efae817d0664604d4e25f0e172cb82 372.919353584000 120345 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": 65316, "vin": [ { "gen": { "height": 65306 } } ], "vout": [ { "amount": 372919353584, "target": { "key": "50c327f4c3b876e2b1187bad89b566e040efae817d0664604d4e25f0e172cb82" } } ], "extra": [ 1, 120, 197, 191, 84, 143, 80, 146, 193, 131, 131, 234, 183, 144, 39, 136, 114, 192, 171, 92, 127, 112, 94, 95, 166, 27, 180, 233, 40, 179, 76, 214, 165, 2, 17, 0, 0, 0, 5, 122, 223, 66, 211, 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