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: 9a2a17743ef46bf2c2338d18b1da8deaa6347204948af42c35a7c11a46b34760
Tx prefix hash: 277909c75d576174e19b10e3c2306701474912af4579b5a5c696d0ee9b42233a
Tx public key: c77d9320d01b0337054907d13afc37b9d384eba4d8e5436b249649438cba928f
| Timestamp: 1780999879 | Timestamp [UTC]: 2026-06-09 10:11:19 | Age [y:d:h:m:s]: 00:000:06:12:40 |
| Block: 8420 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 286 | RingCT/type: yes/0 |
| Extra: 01c77d9320d01b0337054907d13afc37b9d384eba4d8e5436b249649438cba928f020900000001e49593ff00 | ||
1 output(s) for total of 34.623894140552 HMNY
| stealth address | amount | amount idx | tag |
| 00: 36f44ed3e14261a81d4c425b97e69253e3d5da4f4f441816feea005d53ddfb4c | 34.623894140552 | 10408 of 0 | <16> |
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": 8480,
"vin": [ {
"gen": {
"height": 8420
}
}
],
"vout": [ {
"amount": 34623894140552,
"target": {
"tagged_key": {
"key": "36f44ed3e14261a81d4c425b97e69253e3d5da4f4f441816feea005d53ddfb4c",
"view_tag": "16"
}
}
}
],
"extra": [ 1, 199, 125, 147, 32, 208, 27, 3, 55, 5, 73, 7, 209, 58, 252, 55, 185, 211, 132, 235, 164, 216, 229, 67, 107, 36, 150, 73, 67, 140, 186, 146, 143, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}