Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ea6f41d2677249ba23dfa769976d5352a58672cd92e766f0f83f5dc8cb48e4f

Tx prefix hash: 4995cd81b8bbd1d863d1273646b94707ae317bf18340972baf458d92b29633f3
Tx public key: dc80638aa4be49a5b27d47101db5f4b2e07d6cd79ffe12125fb1a5333915a823
Timestamp: 1741594989 Timestamp [UCT]: 2025-03-10 08:23:09 Age [y:d:h:m:s]: 00:302:22:44:03
Block: 1236125 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 214320 RingCT/type: yes/0
Extra: 01dc80638aa4be49a5b27d47101db5f4b2e07d6cd79ffe12125fb1a5333915a8230211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e07e097dfff51da99afe66bc2fd05484a9873f79a2bb2c1a9550fce1e732bc5c 0.600000000000 1723070 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": 1236135, "vin": [ { "gen": { "height": 1236125 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e07e097dfff51da99afe66bc2fd05484a9873f79a2bb2c1a9550fce1e732bc5c" } } ], "extra": [ 1, 220, 128, 99, 138, 164, 190, 73, 165, 178, 125, 71, 16, 29, 181, 244, 178, 224, 125, 108, 215, 159, 254, 18, 18, 95, 177, 165, 51, 57, 21, 168, 35, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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