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: 88656548f126579fe04f39204c58dea9c4a1f745fe4f57be35b710f22c7c9b53
Tx prefix hash: 008443bc96da9fcee47e6329a1d66f557aefaaf80dd306283a719468947574a8
Tx public key: b532504d52e1618a0d43e6b58712f4f7617c530b10ac55afa173f2e1c1c38985
| Timestamp: 1779455815 | Timestamp [UTC]: 2026-05-22 13:16:55 | Age [y:d:h:m:s]: 00:017:13:32:53 |
| Block: 382 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7525 | RingCT/type: yes/0 |
| Extra: 01b532504d52e1618a0d43e6b58712f4f7617c530b10ac55afa173f2e1c1c3898502090000000393369e7d00 | ||
1 output(s) for total of 35.158812875449 HMNY
| stealth address | amount | amount idx | tag |
| 00: 29359f5192159e6537f267c4afd8700b5e103fe4b0ac84701c65fc100c28979e | 35.158812875449 | 380 of 0 | <7f> |
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": 442,
"vin": [ {
"gen": {
"height": 382
}
}
],
"vout": [ {
"amount": 35158812875449,
"target": {
"tagged_key": {
"key": "29359f5192159e6537f267c4afd8700b5e103fe4b0ac84701c65fc100c28979e",
"view_tag": "7f"
}
}
}
],
"extra": [ 1, 181, 50, 80, 77, 82, 225, 97, 138, 13, 67, 230, 181, 135, 18, 244, 247, 97, 124, 83, 11, 16, 172, 85, 175, 161, 115, 242, 225, 193, 195, 137, 133, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}