Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54425bfb9f812605f832f57ea697a002691169c49371e6dea575fdea3aea2144

Tx prefix hash: 538ef6e6a982f6efeaa23e7b2a8f8338c9bd46705c0c70a3ffbe98eca9f7c154
Tx public key: 95c5d892839bdaceac74c80430a15d99d945628085e61684273e22d8e7812205
Timestamp: 1753361519 Timestamp [UCT]: 2025-07-24 12:51:59 Age [y:d:h:m:s]: 00:114:10:31:30
Block: 1332371 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 80616 RingCT/type: yes/0
Extra: 0195c5d892839bdaceac74c80430a15d99d945628085e61684273e22d8e7812205021100000007ef221485000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6bc548ea1564be1e5d4313c866d36b934de1fcf3aae9e5afce5aa98cbafe554c 0.600000000000 1820168 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": 1332381, "vin": [ { "gen": { "height": 1332371 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6bc548ea1564be1e5d4313c866d36b934de1fcf3aae9e5afce5aa98cbafe554c" } } ], "extra": [ 1, 149, 197, 216, 146, 131, 155, 218, 206, 172, 116, 200, 4, 48, 161, 93, 153, 217, 69, 98, 128, 133, 230, 22, 132, 39, 62, 34, 216, 231, 129, 34, 5, 2, 17, 0, 0, 0, 7, 239, 34, 20, 133, 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