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: 35a0097314f8a2df169f32a107f6dc874db9b683bedb67b39a34a0b1e63e251d
Tx prefix hash: 2e32bc53e961c8fb471e071fee63de026f648af794b5c31404dd1d2ba4b4a261
Tx public key: 192c58479c413533423c3027899d3c9109324d0d1f714d9926728c5394ce5d1c
| Timestamp: 1779866551 | Timestamp [UTC]: 2026-05-27 07:22:31 | Age [y:d:h:m:s]: 00:012:13:49:36 |
| Block: 2747 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5139 | RingCT/type: yes/0 |
| Extra: 01192c58479c413533423c3027899d3c9109324d0d1f714d9926728c5394ce5d1c02090000000126697be300 | ||
1 output(s) for total of 35.000572725161 HMNY
| stealth address | amount | amount idx | tag |
| 00: ce425b0d0f376c39678f5b3f4f624a6cfb601f2ac32252c581251d4142b539c8 | 35.000572725161 | 3247 of 0 | <c5> |
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": 2807,
"vin": [ {
"gen": {
"height": 2747
}
}
],
"vout": [ {
"amount": 35000572725161,
"target": {
"tagged_key": {
"key": "ce425b0d0f376c39678f5b3f4f624a6cfb601f2ac32252c581251d4142b539c8",
"view_tag": "c5"
}
}
}
],
"extra": [ 1, 25, 44, 88, 71, 156, 65, 53, 51, 66, 60, 48, 39, 137, 157, 60, 145, 9, 50, 77, 13, 31, 113, 77, 153, 38, 114, 140, 83, 148, 206, 93, 28, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}