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: 6b507c213cf5428243fb756a217d409a6139e5b164f86da72f244d2ae0d555ae
Tx prefix hash: 0d594b436ebc01496f9c32ab041f25e38f7f407fd307356128348e5346469b4e
Tx public key: 732ff0a4dc4a0e83c1b0c3394cc5436470218bd02b10f24d1d3d67d9a5adddfc
| Timestamp: 1779636607 | Timestamp [UTC]: 2026-05-24 15:30:07 | Age [y:d:h:m:s]: 00:015:12:08:43 |
| Block: 1127 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6821 | RingCT/type: yes/0 |
| Extra: 01732ff0a4dc4a0e83c1b0c3394cc5436470218bd02b10f24d1d3d67d9a5adddfc020900000001ba6d17be00 | ||
1 output(s) for total of 35.108888522176 HMNY
| stealth address | amount | amount idx | tag |
| 00: a84d43bdfc72961a133ca3b197312f5daaa278cc0067062d542c3ae48854b10d | 35.108888522176 | 1269 of 0 | <23> |
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": 1187,
"vin": [ {
"gen": {
"height": 1127
}
}
],
"vout": [ {
"amount": 35108888522176,
"target": {
"tagged_key": {
"key": "a84d43bdfc72961a133ca3b197312f5daaa278cc0067062d542c3ae48854b10d",
"view_tag": "23"
}
}
}
],
"extra": [ 1, 115, 47, 240, 164, 220, 74, 14, 131, 193, 176, 195, 57, 76, 197, 67, 100, 112, 33, 139, 208, 43, 16, 242, 77, 29, 61, 103, 217, 165, 173, 221, 252, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}