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: 903468511201ca742dea657167166c8523d240661d4d55431b74dc7088cd0971
Tx prefix hash: 27fbe0fbac5504d9017ab140d9b3ae7fb8ecab9a90d8bbb0b92014ed736fa266
Tx public key: ea5cc606c1c9198dc4f406a31499c624dbaa4e23a7a571663a1fbf45d4328d23
| Timestamp: 1780987464 | Timestamp [UTC]: 2026-06-09 06:44:24 | Age [y:d:h:m:s]: 00:000:06:53:12 |
| Block: 8170 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 431 | RingCT/type: yes/0 |
| Extra: 01ea5cc606c1c9198dc4f406a31499c624dbaa4e23a7a571663a1fbf45d4328d23020900000001e49593ff00 | ||
1 output(s) for total of 34.640408052499 HMNY
| stealth address | amount | amount idx | tag |
| 00: c4f8f608df67f42b8c022a9e7c8edcf48764be94e0b208494207c9b6a3443663 | 34.640408052499 | 10116 of 0 | <56> |
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": 8230,
"vin": [ {
"gen": {
"height": 8170
}
}
],
"vout": [ {
"amount": 34640408052499,
"target": {
"tagged_key": {
"key": "c4f8f608df67f42b8c022a9e7c8edcf48764be94e0b208494207c9b6a3443663",
"view_tag": "56"
}
}
}
],
"extra": [ 1, 234, 92, 198, 6, 193, 201, 25, 141, 196, 244, 6, 163, 20, 153, 198, 36, 219, 170, 78, 35, 167, 165, 113, 102, 58, 31, 191, 69, 212, 50, 141, 35, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}