Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c947b8541b99ce75ecadc514fe5c0197a2a16d14792cf523296a0e627344ec5e

Tx prefix hash: 6f175af7d9f6d31f69b55393ecfdc025060001cef2a904a7f0749dff39c0ffe5
Tx public key: 765f36e6fd0df54eebd46a7b937de516ce52587f2774f1bd84bb81da08ec17a3
Timestamp: 1685119867 Timestamp [UCT]: 2023-05-26 16:51:07 Age [y:d:h:m:s]: 02:021:06:12:58
Block: 768634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 537214 RingCT/type: yes/0
Extra: 01765f36e6fd0df54eebd46a7b937de516ce52587f2774f1bd84bb81da08ec17a3021100000003e6d27f9c000000000000000000

1 output(s) for total of 1.742595783000 dcy

stealth address amount amount idx
00: de837dbb17f8597b8c86769ee3a8eacf0481f79d9eefd3ffa58f5047271f1959 1.742595783000 1217841 of 0

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": 768644, "vin": [ { "gen": { "height": 768634 } } ], "vout": [ { "amount": 1742595783, "target": { "key": "de837dbb17f8597b8c86769ee3a8eacf0481f79d9eefd3ffa58f5047271f1959" } } ], "extra": [ 1, 118, 95, 54, 230, 253, 13, 245, 78, 235, 212, 106, 123, 147, 125, 229, 22, 206, 82, 88, 127, 39, 116, 241, 189, 132, 187, 129, 218, 8, 236, 23, 163, 2, 17, 0, 0, 0, 3, 230, 210, 127, 156, 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