Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ea841017851e61efbc7fd6610879ae698904d53a2d4eed0db87b6d18fdb550d7

Tx prefix hash: 6a3411e383cd1d4164923c6771b1c2fd1fb5f2575db80185f87a71c0334873d7
Tx public key: d314aa3f84e0cbee2fe264bd2922882df6563c7947787f7d26851fcf957c93a3
Timestamp: 1660811979 Timestamp [UCT]: 2022-08-18 08:39:39 Age [y:d:h:m:s]: 02:228:01:40:19
Block: 568406 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 684220 RingCT/type: yes/0
Extra: 01d314aa3f84e0cbee2fe264bd2922882df6563c7947787f7d26851fcf957c93a302110000000175e3f0e9000000000000000000

1 output(s) for total of 8.028512183000 dcy

stealth address amount amount idx
00: 0489ed676d519671d50f69773771dcc04c207beaa2391c1b74096e5553798dea 8.028512183000 1001531 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": 568416, "vin": [ { "gen": { "height": 568406 } } ], "vout": [ { "amount": 8028512183, "target": { "key": "0489ed676d519671d50f69773771dcc04c207beaa2391c1b74096e5553798dea" } } ], "extra": [ 1, 211, 20, 170, 63, 132, 224, 203, 238, 47, 226, 100, 189, 41, 34, 136, 45, 246, 86, 60, 121, 71, 120, 127, 125, 38, 133, 31, 207, 149, 124, 147, 163, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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