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: a3d7477a57e7ec0f4b394da21f1f6daebe08ff993b70dd5b9ba840df6cf15ff5
Tx prefix hash: b0ecb2851510135d38d85b96c4656e69f95810d29d4349807fc59557a882a094
Tx public key: d8d482a91b2f70f90802c9f3082f340a3a40306b4cf58c133d92fc7e5d4c9340
| Timestamp: 1779434468 | Timestamp [UTC]: 2026-05-22 07:21:08 | Age [y:d:h:m:s]: 00:017:20:17:42 |
| Block: 90 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7854 | RingCT/type: yes/0 |
| Extra: 01d8d482a91b2f70f90802c9f3082f340a3a40306b4cf58c133d92fc7e5d4c9340020900000001a662ed0300 | ||
1 output(s) for total of 35.178399901269 HMNY
| stealth address | amount | amount idx | tag |
| 00: 49a0491e6e35f05a1ec34a4fe71bf2bbe69e0e08870bf91cdfcda5f92ecd7449 | 35.178399901269 | 86 of 0 | <e1> |
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": 150,
"vin": [ {
"gen": {
"height": 90
}
}
],
"vout": [ {
"amount": 35178399901269,
"target": {
"tagged_key": {
"key": "49a0491e6e35f05a1ec34a4fe71bf2bbe69e0e08870bf91cdfcda5f92ecd7449",
"view_tag": "e1"
}
}
}
],
"extra": [ 1, 216, 212, 130, 169, 27, 47, 112, 249, 8, 2, 201, 243, 8, 47, 52, 10, 58, 64, 48, 107, 76, 245, 140, 19, 61, 146, 252, 126, 93, 76, 147, 64, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}