Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e75c7ca96389d4c5a5139786dbaec283e8283e08f445e11529cebae3cdbb18ee

Tx prefix hash: a058cd255d3887fc01b4248e4fb3678d22e1d0c4775abf8f7e24e97cc6002b93
Tx public key: f60c98857caa56e6d984abcfae80fb252b3b1b72102225698096a72a0307f0b7
Timestamp: 1581976238 Timestamp [UCT]: 2020-02-17 21:50:38 Age [y:d:h:m:s]: 04:316:02:46:26
Block: 67047 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1118316 RingCT/type: yes/0
Extra: 01f60c98857caa56e6d984abcfae80fb252b3b1b72102225698096a72a0307f0b7021100000018d81c26c0000000000000000000

1 output(s) for total of 367.998683048000 dcy

stealth address amount amount idx
00: 11eee75ad87efce93204caa332da3236627b3584d8ca1c9eb10b1ce39deeb00a 367.998683048000 123497 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": 67057, "vin": [ { "gen": { "height": 67047 } } ], "vout": [ { "amount": 367998683048, "target": { "key": "11eee75ad87efce93204caa332da3236627b3584d8ca1c9eb10b1ce39deeb00a" } } ], "extra": [ 1, 246, 12, 152, 133, 124, 170, 86, 230, 217, 132, 171, 207, 174, 128, 251, 37, 43, 59, 27, 114, 16, 34, 37, 105, 128, 150, 167, 42, 3, 7, 240, 183, 2, 17, 0, 0, 0, 24, 216, 28, 38, 192, 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