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: b6bec26e64aeea4c0e4728786ee7470f04b3993c75e2a75dec942930bd0ff793
Tx prefix hash: 72bba0640015e536d54dc161af98230b9b883ef0250337fc67dd383d9c5ceb5d
Tx public key: cc66ed6b2cf915ae975f0c2371132ea52a57e8c3123524f70d108e4f68292271
| Timestamp: 1780823493 | Timestamp [UTC]: 2026-06-07 09:11:33 | Age [y:d:h:m:s]: 00:001:15:35:14 |
| Block: 7218 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 668 | RingCT/type: yes/0 |
| Extra: 01cc66ed6b2cf915ae975f0c2371132ea52a57e8c3123524f70d108e4f68292271020900000002e49593ff00 | ||
1 output(s) for total of 34.703365164737 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2f8c38fa2291c75f699a9e9823ec7b43197eb4a6902eef37f3b0af407800d270 | 34.703365164737 | 8890 of 0 | <9b> |
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": 7278,
"vin": [ {
"gen": {
"height": 7218
}
}
],
"vout": [ {
"amount": 34703365164737,
"target": {
"tagged_key": {
"key": "2f8c38fa2291c75f699a9e9823ec7b43197eb4a6902eef37f3b0af407800d270",
"view_tag": "9b"
}
}
}
],
"extra": [ 1, 204, 102, 237, 107, 44, 249, 21, 174, 151, 95, 12, 35, 113, 19, 46, 165, 42, 87, 232, 195, 18, 53, 36, 247, 13, 16, 142, 79, 104, 41, 34, 113, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}