Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8f9e2054c2b447ed8ccb8c4d001e4662b350775652307ccb7b4c73c012de2333

Tx prefix hash: 1f9c3208914b90669332d3e1f761b8663bd4c6a96fa5ab3d821fa51d54cf8c97
Tx public key: 6586ed82d5c9b9938c73ac41e68a4c79ac31c3387af7a9c2aac7f89066fef41e
Timestamp: 1698079010 Timestamp [UCT]: 2023-10-23 16:36:50 Age [y:d:h:m:s]: 01:153:12:07:00
Block: 876020 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 370713 RingCT/type: yes/0
Extra: 016586ed82d5c9b9938c73ac41e68a4c79ac31c3387af7a9c2aac7f89066fef41e02110000000375e3f0e9000000000000000000

1 output(s) for total of 0.768036934000 dcy

stealth address amount amount idx
00: f0f0c6fe873752cde125cb0e94e8b240bea679d1e69a058c88f7a05f5daf63b4 0.768036934000 1331328 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": 876030, "vin": [ { "gen": { "height": 876020 } } ], "vout": [ { "amount": 768036934, "target": { "key": "f0f0c6fe873752cde125cb0e94e8b240bea679d1e69a058c88f7a05f5daf63b4" } } ], "extra": [ 1, 101, 134, 237, 130, 213, 201, 185, 147, 140, 115, 172, 65, 230, 138, 76, 121, 172, 49, 195, 56, 122, 247, 169, 194, 170, 199, 248, 144, 102, 254, 244, 30, 2, 17, 0, 0, 0, 3, 117, 227, 240, 233, 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