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: 2ac7f678841f2ed54acd847bac4df8807b83d0e61ae664b93bd0ebb0024607f7
Tx prefix hash: d5d1a1bc84ad2c644fa3c3f770a70bb3075d9eb31e1257ac9ea4b4a761cb2c62
Tx public key: 0b6bde63d88ba867b1dfb065b48ba6db382a07a9d91751e557462024dd0d4921
| Timestamp: 1780846312 | Timestamp [UTC]: 2026-06-07 15:31:52 | Age [y:d:h:m:s]: 00:001:09:14:55 |
| Block: 7510 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 376 | RingCT/type: yes/0 |
| Extra: 010b6bde63d88ba867b1dfb065b48ba6db382a07a9d91751e557462024dd0d4921020900000003e49593ff00 | ||
1 output(s) for total of 34.684042634109 HMNY
| stealth address | amount | amount idx | tag |
| 00: 506d6f3ca7eca660ba65e55ce9c8b393e6c0d521afe22b5a6f113b406bbb77c6 | 34.684042634109 | 9258 of 0 | <37> |
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": 7570,
"vin": [ {
"gen": {
"height": 7510
}
}
],
"vout": [ {
"amount": 34684042634109,
"target": {
"tagged_key": {
"key": "506d6f3ca7eca660ba65e55ce9c8b393e6c0d521afe22b5a6f113b406bbb77c6",
"view_tag": "37"
}
}
}
],
"extra": [ 1, 11, 107, 222, 99, 216, 139, 168, 103, 177, 223, 176, 101, 180, 139, 166, 219, 56, 42, 7, 169, 217, 23, 81, 229, 87, 70, 32, 36, 221, 13, 73, 33, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}