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: 9a6d24c9cae2cd6d2ebd79581bcd9c47d6f9ff864879ea60f54fd62d96335bce
Tx prefix hash: c2273e51fd10448567664fd40097db6216ebeb92311c50faacbc74be6cac176d
Tx public key: a2a739fa0f71c8278939d3d3f5d1edc08df35955613bcb48872327b90ddc7413
| Timestamp: 1780391256 | Timestamp [UTC]: 2026-06-02 09:07:36 | Age [y:d:h:m:s]: 00:007:08:01:27 |
| Block: 5213 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3522 | RingCT/type: yes/0 |
| Extra: 01a2a739fa0f71c8278939d3d3f5d1edc08df35955613bcb48872327b90ddc741302090000000326697be300 | ||
1 output(s) for total of 34.836333169158 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1a0b0ae2285a2667d65f244da52e08e4456afb27bdc5816f237b2982bd49a89d | 34.836333169158 | 6594 of 0 | <40> |
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": 5273,
"vin": [ {
"gen": {
"height": 5213
}
}
],
"vout": [ {
"amount": 34836333169158,
"target": {
"tagged_key": {
"key": "1a0b0ae2285a2667d65f244da52e08e4456afb27bdc5816f237b2982bd49a89d",
"view_tag": "40"
}
}
}
],
"extra": [ 1, 162, 167, 57, 250, 15, 113, 200, 39, 137, 57, 211, 211, 245, 209, 237, 192, 141, 243, 89, 85, 97, 59, 203, 72, 135, 35, 39, 185, 13, 220, 116, 19, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}