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: 5e2eb04b3a7f1bde67d11cc08f39a202d62423ce124cf6e15e54ddabcf65c8a3
Tx prefix hash: dba230f4c413d0f2483d5c7ce444f563f27abcf7deb5112fccbff01a30b66d7b
Tx public key: 6abf8142a62525d691dd618eb7db65521ecc169a77f216f2433738d5babe0428
| Timestamp: 1779462814 | Timestamp [UTC]: 2026-05-22 15:13:34 | Age [y:d:h:m:s]: 00:017:13:19:28 |
| Block: 468 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7558 | RingCT/type: yes/0 |
| Extra: 016abf8142a62525d691dd618eb7db65521ecc169a77f216f2433738d5babe042802090000000293369e7d00 | ||
1 output(s) for total of 35.153046173148 HMNY
| stealth address | amount | amount idx | tag |
| 00: 51807ff5645c6a9b94d4ad10b057e7166ac7e763fd9b35e54f2fa2c213f98cef | 35.153046173148 | 472 of 0 | <af> |
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": 528,
"vin": [ {
"gen": {
"height": 468
}
}
],
"vout": [ {
"amount": 35153046173148,
"target": {
"tagged_key": {
"key": "51807ff5645c6a9b94d4ad10b057e7166ac7e763fd9b35e54f2fa2c213f98cef",
"view_tag": "af"
}
}
}
],
"extra": [ 1, 106, 191, 129, 66, 166, 37, 37, 214, 145, 221, 97, 142, 183, 219, 101, 82, 30, 204, 22, 154, 119, 242, 22, 242, 67, 55, 56, 213, 186, 190, 4, 40, 2, 9, 0, 0, 0, 2, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}