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: bb326199e4de978512874e474df409a76a4eaee9f0aa8e6205117f966d014aca
Tx prefix hash: 66f8d16b535b10a67c83c209694c4f91c46f57ae9cdd8f72659cd8d354299ea2
Tx public key: ee8f74fdff65e7436302f756782426bcc501c791ef5cc0b4bb8122afc463bf9d
| Timestamp: 1780691698 | Timestamp [UTC]: 2026-06-05 20:34:58 | Age [y:d:h:m:s]: 00:003:04:11:49 |
| Block: 5746 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2140 | RingCT/type: yes/0 |
| Extra: 01ee8f74fdff65e7436302f756782426bcc501c791ef5cc0b4bb8122afc463bf9d020900000001e49593ff00 | ||
1 output(s) for total of 34.800935928872 HMNY
| stealth address | amount | amount idx | tag |
| 00: 72972fc27a04c7862343d6d7634f09135a076038c16b094996c32a873938a41b | 34.800935928872 | 7199 of 0 | <b4> |
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": 5806,
"vin": [ {
"gen": {
"height": 5746
}
}
],
"vout": [ {
"amount": 34800935928872,
"target": {
"tagged_key": {
"key": "72972fc27a04c7862343d6d7634f09135a076038c16b094996c32a873938a41b",
"view_tag": "b4"
}
}
}
],
"extra": [ 1, 238, 143, 116, 253, 255, 101, 231, 67, 99, 2, 247, 86, 120, 36, 38, 188, 197, 1, 199, 145, 239, 92, 192, 180, 187, 129, 34, 175, 196, 99, 191, 157, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}