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: b9219b49f9dd8c8c5f3e1142ba4e9e5164f2146a030842ba23d0a287d9bd75fe
Tx prefix hash: 19bcecfbde56af61da86523cf024be1d2e6e69ddbbd104f9c60941c04e540a3d
Tx public key: 70b4f8b0cfeeae1db3b0df0fc332bbe76f355f141472dbc9157290d9b0f21a1f
| Timestamp: 1780030162 | Timestamp [UTC]: 2026-05-29 04:49:22 | Age [y:d:h:m:s]: 00:010:19:57:25 |
| Block: 4194 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3692 | RingCT/type: yes/0 |
| Extra: 0170b4f8b0cfeeae1db3b0df0fc332bbe76f355f141472dbc9157290d9b0f21a1f02090000000126697be300 | ||
1 output(s) for total of 34.904106562301 HMNY
| stealth address | amount | amount idx | tag |
| 00: ba71a689c55d55dc9e94b67727cd0889051c986e78568cd74ea3b8fc4d41df28 | 34.904106562301 | 5227 of 0 | <b4> |
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": 4254,
"vin": [ {
"gen": {
"height": 4194
}
}
],
"vout": [ {
"amount": 34904106562301,
"target": {
"tagged_key": {
"key": "ba71a689c55d55dc9e94b67727cd0889051c986e78568cd74ea3b8fc4d41df28",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 112, 180, 248, 176, 207, 238, 174, 29, 179, 176, 223, 15, 195, 50, 187, 231, 111, 53, 95, 20, 20, 114, 219, 201, 21, 114, 144, 217, 176, 242, 26, 31, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}