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: c8f58506bf67456f5aea83166f23cab331c1cf29f3d45a9e141f4e6759f64db2
Tx prefix hash: c686fc404dc32e0c8f4f9d9e257cfb7dc400a5de13b67dc5f4651b3c662ffc49
Tx public key: ef60872a2b4a07269d0c8f135616f5b43fbb9439ae67ef4a24dc9a34058de6f6
| Timestamp: 1780998334 | Timestamp [UTC]: 2026-06-09 09:45:34 | Age [y:d:h:m:s]: 00:000:13:36:00 |
| Block: 8392 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 353 | RingCT/type: yes/0 |
| Extra: 01ef60872a2b4a07269d0c8f135616f5b43fbb9439ae67ef4a24dc9a34058de6f6020900000001e49593ff00 | ||
1 output(s) for total of 34.625743307134 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3082704096a847613e8f7b38d308319704f33c73b0f04ff9e9deb68aa8bf026b | 34.625743307134 | 10374 of 0 | <46> |
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": 8452,
"vin": [ {
"gen": {
"height": 8392
}
}
],
"vout": [ {
"amount": 34625743307134,
"target": {
"tagged_key": {
"key": "3082704096a847613e8f7b38d308319704f33c73b0f04ff9e9deb68aa8bf026b",
"view_tag": "46"
}
}
}
],
"extra": [ 1, 239, 96, 135, 42, 43, 74, 7, 38, 157, 12, 143, 19, 86, 22, 245, 180, 63, 187, 148, 57, 174, 103, 239, 74, 36, 220, 154, 52, 5, 141, 230, 246, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}