Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2856b282d5f630b6e5ec32484eb5ebdc9be63d43be3c001b5f1613dd35c594e

Tx prefix hash: 671fe66febba2cb76d4f48c1ecd59bd824a3c92e1582362d6abfc4a9c36cd934
Tx public key: 01061bc589758518b7e24560b7bee3943db9e8c92632fad1bdb457ba33222ab8
Timestamp: 1708648738 Timestamp [UCT]: 2024-02-23 00:38:58 Age [y:d:h:m:s]: 01:047:01:55:17
Block: 963445 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 294675 RingCT/type: yes/0
Extra: 0101061bc589758518b7e24560b7bee3943db9e8c92632fad1bdb457ba33222ab80211000000097a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4ec4902d9839d52827254c1a7dbd8ecf57db3fc8adf495c15b55f8514c5a7359 0.600000000000 1423156 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": 963455, "vin": [ { "gen": { "height": 963445 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4ec4902d9839d52827254c1a7dbd8ecf57db3fc8adf495c15b55f8514c5a7359" } } ], "extra": [ 1, 1, 6, 27, 197, 137, 117, 133, 24, 183, 226, 69, 96, 183, 190, 227, 148, 61, 185, 232, 201, 38, 50, 250, 209, 189, 180, 87, 186, 51, 34, 42, 184, 2, 17, 0, 0, 0, 9, 122, 156, 244, 199, 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