Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6265e4b20383e7f53e9b9bb385744b98b5cb2fa4b3fa4e391bcfc357e62fe624

Tx prefix hash: 08c69d8b543b1ecc406fffcbe8c4454974893baf46f88e9f39147210bb462758
Tx public key: ebf72e98a265a118598be961cbc7a9adc4a61d594b56b89d7c2b29062d6c43d0
Timestamp: 1752399377 Timestamp [UCT]: 2025-07-13 09:36:17 Age [y:d:h:m:s]: 00:196:17:47:12
Block: 1324514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 139242 RingCT/type: yes/0
Extra: 01ebf72e98a265a118598be961cbc7a9adc4a61d594b56b89d7c2b29062d6c43d00211000000038368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e8e7c9eded9d4260b25303699dcc9b20b3cf4a53aa1a417c09f4be2fd94224ca 0.600000000000 1812257 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": 1324524, "vin": [ { "gen": { "height": 1324514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e8e7c9eded9d4260b25303699dcc9b20b3cf4a53aa1a417c09f4be2fd94224ca" } } ], "extra": [ 1, 235, 247, 46, 152, 162, 101, 161, 24, 89, 139, 233, 97, 203, 199, 169, 173, 196, 166, 29, 89, 75, 86, 184, 157, 124, 43, 41, 6, 45, 108, 67, 208, 2, 17, 0, 0, 0, 3, 131, 104, 38, 109, 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