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: e7758629ea0eb897ca532c4b817d89ed6daca4dee63f5807f84fa17b9354741e
Tx prefix hash: 9004022dd8ba058f100c6d530d4ea69bed6a2d738806ec62e0e8fb944708d1cb
Tx public key: 253314896a7c4ab13c435c100d9380ccbb58bcb5d19a39b2861b5a6ee30fd11d
| Timestamp: 1780846803 | Timestamp [UTC]: 2026-06-07 15:40:03 | Age [y:d:h:m:s]: 00:002:01:29:00 |
| Block: 7513 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1222 | RingCT/type: yes/0 |
| Extra: 01253314896a7c4ab13c435c100d9380ccbb58bcb5d19a39b2861b5a6ee30fd11d020900000001e49593ff00 | ||
1 output(s) for total of 34.688064570803 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7b512dc87550d58c924fc24791b6fa87a92dae2bbbcada142d554be8929babcd | 34.688064570803 | 9261 of 0 | <22> |
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": 7573,
"vin": [ {
"gen": {
"height": 7513
}
}
],
"vout": [ {
"amount": 34688064570803,
"target": {
"tagged_key": {
"key": "7b512dc87550d58c924fc24791b6fa87a92dae2bbbcada142d554be8929babcd",
"view_tag": "22"
}
}
}
],
"extra": [ 1, 37, 51, 20, 137, 106, 124, 74, 177, 60, 67, 92, 16, 13, 147, 128, 204, 187, 88, 188, 181, 209, 154, 57, 178, 134, 27, 90, 110, 227, 15, 209, 29, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}