Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f36eabc180953d13360f284a42e90bb385c2f562591e6ec5ced3d75be6d72b8b

Tx prefix hash: 6fe75f2c56dd6710750e551d50cfc2461ea790ba74436cf60314c3606371203d
Tx public key: 531661c06c9df1b51ff86f6a186203d040e7edd7de56b112ac3eff39ff63d392
Timestamp: 1577786043 Timestamp [UCT]: 2019-12-31 09:54:03 Age [y:d:h:m:s]: 04:330:17:40:44
Block: 35595 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1125540 RingCT/type: yes/0
Extra: 01531661c06c9df1b51ff86f6a186203d040e7edd7de56b112ac3eff39ff63d39202110000000a8a2ee0d9000000000000000000

1 output(s) for total of 467.799596529000 dcy

stealth address amount amount idx
00: 7d8f28bd041d7acd974a4de1485b62a73bd7e93cef63a712628e3302131f3b7a 467.799596529000 60094 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": 35605, "vin": [ { "gen": { "height": 35595 } } ], "vout": [ { "amount": 467799596529, "target": { "key": "7d8f28bd041d7acd974a4de1485b62a73bd7e93cef63a712628e3302131f3b7a" } } ], "extra": [ 1, 83, 22, 97, 192, 108, 157, 241, 181, 31, 248, 111, 106, 24, 98, 3, 208, 64, 231, 237, 215, 222, 86, 177, 18, 172, 62, 255, 57, 255, 99, 211, 146, 2, 17, 0, 0, 0, 10, 138, 46, 224, 217, 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