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: 15abfb8d7eb01cdbc30d1fe60ad77b8544bf00de385438a8a3043ff6e84e5b74
Tx prefix hash: b34d01cfae4d92d90e189eff6bfde07376a2a7adfb42692ab0aafaee7fac77b2
Tx public key: e38f2a5aefc69c3439602072eeaf8bc8e25fb5c18fe515412f82d002da09bcc8
| Timestamp: 1780713331 | Timestamp [UTC]: 2026-06-06 02:35:31 | Age [y:d:h:m:s]: 00:002:22:11:16 |
| Block: 6171 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1715 | RingCT/type: yes/0 |
| Extra: 01e38f2a5aefc69c3439602072eeaf8bc8e25fb5c18fe515412f82d002da09bcc8020900000001e49593ff00 | ||
1 output(s) for total of 34.772736887956 HMNY
| stealth address | amount | amount idx | tag |
| 00: d97611cc9255e69dc86535da1f7c7c628955616e849760e947250e45adb8dd15 | 34.772736887956 | 7648 of 0 | <f4> |
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": 6231,
"vin": [ {
"gen": {
"height": 6171
}
}
],
"vout": [ {
"amount": 34772736887956,
"target": {
"tagged_key": {
"key": "d97611cc9255e69dc86535da1f7c7c628955616e849760e947250e45adb8dd15",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 227, 143, 42, 90, 239, 198, 156, 52, 57, 96, 32, 114, 238, 175, 139, 200, 226, 95, 181, 193, 143, 229, 21, 65, 47, 130, 208, 2, 218, 9, 188, 200, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}