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: fa5464ebfb2ccbd6b3108bf42f34fc4c27674209317c3d20df8d62e6c9510c19
Tx prefix hash: 3808add532cf1a7a84220796ba7c16e77f8e27b1ba1d672a3956a86c7fdc2de3
Tx public key: 5b3af3b88a34f18924487cf5c0116d2df7e2aa7cae94d0e1c31472c7c82edac5
| Timestamp: 1780834639 | Timestamp [UTC]: 2026-06-07 12:17:19 | Age [y:d:h:m:s]: 00:005:23:03:46 |
| Block: 7388 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1357 | RingCT/type: yes/0 |
| Extra: 015b3af3b88a34f18924487cf5c0116d2df7e2aa7cae94d0e1c31472c7c82edac5020900000001e49593ff00 | ||
1 output(s) for total of 34.692114437389 HMNY
| stealth address | amount | amount idx | tag |
| 00: c70ef82973289e26d2b1364f97da4dba905a0e524999a7bdabfd6dcffe057426 | 34.692114437389 | 9096 of 0 | <00> |
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": 7448,
"vin": [ {
"gen": {
"height": 7388
}
}
],
"vout": [ {
"amount": 34692114437389,
"target": {
"tagged_key": {
"key": "c70ef82973289e26d2b1364f97da4dba905a0e524999a7bdabfd6dcffe057426",
"view_tag": "00"
}
}
}
],
"extra": [ 1, 91, 58, 243, 184, 138, 52, 241, 137, 36, 72, 124, 245, 192, 17, 109, 45, 247, 226, 170, 124, 174, 148, 208, 225, 195, 20, 114, 199, 200, 46, 218, 197, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}