Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 884dc7a496c1789ee9b35869565585bdf9b37eeb1bcd637d77bc5f806c269f67

Tx prefix hash: ccbec3377566f533cdf45f9f2de33038939a2f16b089df6579ad4a34acb90cf4
Tx public key: 9af00fa6cc75a35b43a4addd4a1b6ecb1c7165b3cf089b80182de9b86eff0a03
Timestamp: 1766004541 Timestamp [UCT]: 2025-12-17 20:49:01 Age [y:d:h:m:s]: 00:045:17:27:31
Block: 1435818 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 32565 RingCT/type: yes/0
Extra: 019af00fa6cc75a35b43a4addd4a1b6ecb1c7165b3cf089b80182de9b86eff0a03021100000002d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b6fc1a7bf69a26b90bf0139fe67932e0f948274731a6ddc55719393eb9d24612 0.600000000000 1924623 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": 1435828, "vin": [ { "gen": { "height": 1435818 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b6fc1a7bf69a26b90bf0139fe67932e0f948274731a6ddc55719393eb9d24612" } } ], "extra": [ 1, 154, 240, 15, 166, 204, 117, 163, 91, 67, 164, 173, 221, 74, 27, 110, 203, 28, 113, 101, 179, 207, 8, 155, 128, 24, 45, 233, 184, 110, 255, 10, 3, 2, 17, 0, 0, 0, 2, 214, 225, 157, 124, 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