Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fa83d479e4370e9bffabbe3d8a79c934464f71fc6cf1d6faa4eecf8d7df6eb7e

Tx prefix hash: bea4c1ed03549b569aae63d15f091f422b5e9a6557f71d533c52573e23c42b65
Tx public key: facecfbd02d6ec0a5b7559b4570e2dedd877c1b63c43ce82fd05c14b20f77d01
Timestamp: 1758790559 Timestamp [UCT]: 2025-09-25 08:55:59 Age [y:d:h:m:s]: 00:120:05:55:09
Block: 1376036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85963 RingCT/type: yes/0
Extra: 01facecfbd02d6ec0a5b7559b4570e2dedd877c1b63c43ce82fd05c14b20f77d01021100000004ad7948d0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c9e0c9ace6d4fedffe68c9e58e92dd942bc12b571fad79c755f890eb6f36e153 0.600000000000 1864127 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": 1376046, "vin": [ { "gen": { "height": 1376036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c9e0c9ace6d4fedffe68c9e58e92dd942bc12b571fad79c755f890eb6f36e153" } } ], "extra": [ 1, 250, 206, 207, 189, 2, 214, 236, 10, 91, 117, 89, 180, 87, 14, 45, 237, 216, 119, 193, 182, 60, 67, 206, 130, 253, 5, 193, 75, 32, 247, 125, 1, 2, 17, 0, 0, 0, 4, 173, 121, 72, 208, 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