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: e116425339415ce17859b03a0e22de8bc3faa39ef889fc01a7c9874f01b1633e
Tx prefix hash: b24397daddfbd217ecd9056ddf6cbf6f1f830ca8f7016ee316d5cf5a9e2f37e4
Tx public key: b1c03666291239902ed4897fd1aba63cb4f256f8cbf36d8cecaa2aadd67a2c8b
| Timestamp: 1780743394 | Timestamp [UTC]: 2026-06-06 10:56:34 | Age [y:d:h:m:s]: 00:002:16:42:16 |
| Block: 6431 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1516 | RingCT/type: yes/0 |
| Extra: 01b1c03666291239902ed4897fd1aba63cb4f256f8cbf36d8cecaa2aadd67a2c8b020900000002e49593ff00 | ||
1 output(s) for total of 34.755496976234 HMNY
| stealth address | amount | amount idx | tag |
| 00: a4195619187a4017d21ef9c997de42d72bf1a07282853725f2e5bb08787a4ea1 | 34.755496976234 | 7924 of 0 | <2d> |
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": 6491,
"vin": [ {
"gen": {
"height": 6431
}
}
],
"vout": [ {
"amount": 34755496976234,
"target": {
"tagged_key": {
"key": "a4195619187a4017d21ef9c997de42d72bf1a07282853725f2e5bb08787a4ea1",
"view_tag": "2d"
}
}
}
],
"extra": [ 1, 177, 192, 54, 102, 41, 18, 57, 144, 46, 212, 137, 127, 209, 171, 166, 60, 180, 242, 86, 248, 203, 243, 109, 140, 236, 170, 42, 173, 214, 122, 44, 139, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}