Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f32a6081d9e59c934c26908bf4ffea6ef1d13c956fa55c29c47472d6727a0bd1

Tx prefix hash: 42e6ffdac8a913a161cc076d8e4cfb188e313c31b8aa12540b4401c05a0f7b8e
Tx public key: 83eba1789c5e776301d002c010bd94b789bccfd7f4cf7e281bcbd79137d820db
Timestamp: 1697098801 Timestamp [UCT]: 2023-10-12 08:20:01 Age [y:d:h:m:s]: 01:182:14:31:19
Block: 867900 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 391546 RingCT/type: yes/0
Extra: 0183eba1789c5e776301d002c010bd94b789bccfd7f4cf7e281bcbd79137d820db02110000000833af99f4000000000000000000

1 output(s) for total of 0.817122272000 dcy

stealth address amount amount idx
00: 9bffce9e73a1d5bf2ac70b902b33d32edab2f2a87bc36752920be459a3f47574 0.817122272000 1322633 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": 867910, "vin": [ { "gen": { "height": 867900 } } ], "vout": [ { "amount": 817122272, "target": { "key": "9bffce9e73a1d5bf2ac70b902b33d32edab2f2a87bc36752920be459a3f47574" } } ], "extra": [ 1, 131, 235, 161, 120, 156, 94, 119, 99, 1, 208, 2, 192, 16, 189, 148, 183, 137, 188, 207, 215, 244, 207, 126, 40, 27, 203, 215, 145, 55, 216, 32, 219, 2, 17, 0, 0, 0, 8, 51, 175, 153, 244, 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