Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ca5612e4f6243c57d5af20549db49dbf8a9957920fd69f75ad248a52471bb12

Tx prefix hash: 5cd42b2172b9d52a897be384b0db6710422d8e1c75089bf7d83309027ca2ef1c
Tx public key: d95b35410a50203616263a599ae0b0c7c7e527697688715c7ca861b8a0a959ee
Timestamp: 1724804461 Timestamp [UCT]: 2024-08-28 00:21:01 Age [y:d:h:m:s]: 01:128:18:10:00
Block: 1097383 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 350550 RingCT/type: yes/0
Extra: 01d95b35410a50203616263a599ae0b0c7c7e527697688715c7ca861b8a0a959ee021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d6ff5aa9bfb157ecd1a807883fcbce4505d6a28da33054764cb016a9b6160f13 0.600000000000 1572778 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": 1097393, "vin": [ { "gen": { "height": 1097383 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d6ff5aa9bfb157ecd1a807883fcbce4505d6a28da33054764cb016a9b6160f13" } } ], "extra": [ 1, 217, 91, 53, 65, 10, 80, 32, 54, 22, 38, 58, 89, 154, 224, 176, 199, 199, 229, 39, 105, 118, 136, 113, 92, 124, 168, 97, 184, 160, 169, 89, 238, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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