For RingCT transactions, outputs' amounts are also decoded
Tx private key can be obtained using get_tx_key
command in hashmonkey-wallet-cli command line tool
Tx hash: b1359cfe08ff17d2a25d57c6c38ee5a7c186b15d21cda507b6e31cb741db0c8c
Tx prefix hash: abe429e3cdfbb89625e2d6151e5f3103d735809d231cad5c754cfbee705a55f0
Tx public key: d7c7cfc153c52a56c34ef46663f7ca96b49dc77b5292518ebb8aadff3dde01e0
| Timestamp: 1780990563 | Timestamp [UTC]: 2026-06-09 07:36:03 | Age [y:d:h:m:s]: 00:000:06:01:33 |
| Block: 8224 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 377 | RingCT/type: yes/0 |
| Extra: 01d7c7cfc153c52a56c34ef46663f7ca96b49dc77b5292518ebb8aadff3dde01e0020900000001e49593ff00 | ||
1 output(s) for total of 34.636840380743 HMNY
| stealth address | amount | amount idx | tag |
| 00: eb51dfcde4b4272ea5f087041d7b5a0b879a25fbc759be0a31774b2328ed181f | 34.636840380743 | 10180 of 0 | <ad> |
Check which outputs belong to given HMNY 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 HMNY in this transaction
Tx private key can be obtained using get_tx_key
command in hashmonkey-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": 8284,
"vin": [ {
"gen": {
"height": 8224
}
}
],
"vout": [ {
"amount": 34636840380743,
"target": {
"tagged_key": {
"key": "eb51dfcde4b4272ea5f087041d7b5a0b879a25fbc759be0a31774b2328ed181f",
"view_tag": "ad"
}
}
}
],
"extra": [ 1, 215, 199, 207, 193, 83, 197, 42, 86, 195, 78, 244, 102, 99, 247, 202, 150, 180, 157, 199, 123, 82, 146, 81, 142, 187, 138, 173, 255, 61, 222, 1, 224, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}