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: 2ec8ab027b2823dd4e2bb3951dde6ef1f8d609d501acd8ffc30a1102fe4d9b2e
Tx prefix hash: b9f9d86ac359b38459b9fa2addd105427f3ed473cd5119bb8b3a4d846d5d8c6c
Tx public key: 666a116927849cc78a8ab7075378655ba82589cd69d44d8baa4315c7c71c4cd8
| Timestamp: 1780851806 | Timestamp [UTC]: 2026-06-07 17:03:26 | Age [y:d:h:m:s]: 00:005:18:17:39 |
| Block: 7546 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1199 | RingCT/type: yes/0 |
| Extra: 01666a116927849cc78a8ab7075378655ba82589cd69d44d8baa4315c7c71c4cd8020900000001e49593ff00 | ||
1 output(s) for total of 34.681661149394 HMNY
| stealth address | amount | amount idx | tag |
| 00: 240dc6535092cf4b805065563a6f964b9bcbfa256f62602284c5e7f56c4ebb35 | 34.681661149394 | 9312 of 0 | <a1> |
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": 7606,
"vin": [ {
"gen": {
"height": 7546
}
}
],
"vout": [ {
"amount": 34681661149394,
"target": {
"tagged_key": {
"key": "240dc6535092cf4b805065563a6f964b9bcbfa256f62602284c5e7f56c4ebb35",
"view_tag": "a1"
}
}
}
],
"extra": [ 1, 102, 106, 17, 105, 39, 132, 156, 199, 138, 138, 183, 7, 83, 120, 101, 91, 168, 37, 137, 205, 105, 212, 77, 139, 170, 67, 21, 199, 199, 28, 76, 216, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}