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: 283a539f3820f3fbad05345765defef950adb27948eba43c56d6ff36999c4ee4
Tx prefix hash: 2b8d310ba234b4739c1a6ecc99882ab44cebaae140ff01741bee2c6f09c5dfb1
Tx public key: 1c9aaeeb36166aaab3d235a5bfd1d279044d388e37d49860802fd306c470a48b
| Timestamp: 1780042124 | Timestamp [UTC]: 2026-05-29 08:08:44 | Age [y:d:h:m:s]: 00:010:19:42:14 |
| Block: 4300 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3650 | RingCT/type: yes/0 |
| Extra: 011c9aaeeb36166aaab3d235a5bfd1d279044d388e37d49860802fd306c470a48b02090000000326697be300 | ||
1 output(s) for total of 34.897050393108 HMNY
| stealth address | amount | amount idx | tag |
| 00: b5ff44b3b7ec192f3a943a5c14de8191be460d87fc385496049308756e92501b | 34.897050393108 | 5374 of 0 | <31> |
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": 4360,
"vin": [ {
"gen": {
"height": 4300
}
}
],
"vout": [ {
"amount": 34897050393108,
"target": {
"tagged_key": {
"key": "b5ff44b3b7ec192f3a943a5c14de8191be460d87fc385496049308756e92501b",
"view_tag": "31"
}
}
}
],
"extra": [ 1, 28, 154, 174, 235, 54, 22, 106, 170, 179, 210, 53, 165, 191, 209, 210, 121, 4, 77, 56, 142, 55, 212, 152, 96, 128, 47, 211, 6, 196, 112, 164, 139, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}