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: add8d03aebe30d1e40591f3a21beb128c17a364e5d41f66e08ca339369c8b924
Tx prefix hash: eb84540e4b3009ff96b53c126feadfe89b16dae8756b8a7b168a4174f1349c9e
Tx public key: 6a35b38ebc70999fcdeb1db3d7a3e4d0c9e2f92b8560ec1f53498936d2235789
| Timestamp: 1780973367 | Timestamp [UTC]: 2026-06-09 02:49:27 | Age [y:d:h:m:s]: 00:000:08:45:07 |
| Block: 7898 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 638 | RingCT/type: yes/0 |
| Extra: 016a35b38ebc70999fcdeb1db3d7a3e4d0c9e2f92b8560ec1f53498936d2235789020900000001e49593ff00 | ||
1 output(s) for total of 34.663413335328 HMNY
| stealth address | amount | amount idx | tag |
| 00: c3f6b5c42e12859d1538dc58b4ddc7a213cb90885d8c459fe1618895f40b7a67 | 34.663413335328 | 9794 of 0 | <8e> |
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": 7958,
"vin": [ {
"gen": {
"height": 7898
}
}
],
"vout": [ {
"amount": 34663413335328,
"target": {
"tagged_key": {
"key": "c3f6b5c42e12859d1538dc58b4ddc7a213cb90885d8c459fe1618895f40b7a67",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 106, 53, 179, 142, 188, 112, 153, 159, 205, 235, 29, 179, 215, 163, 228, 208, 201, 226, 249, 43, 133, 96, 236, 31, 83, 73, 137, 54, 210, 35, 87, 137, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}