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: b1f78fe31d6bf210ad118095446d402658bad9835e89de7cc1b0a80a4e897ff6
Tx prefix hash: 50cf6ead39340049cd5d76f2c444a78c1b144b789c0eed6ae7a12610700fc9c6
Tx public key: 1096a9ea6c8d907dd427d9d393afbec2bb7aed4aae210f43610b7dd6f1665c9d
| Timestamp: 1779783326 | Timestamp [UTC]: 2026-05-26 08:15:26 | Age [y:d:h:m:s]: 00:013:19:23:24 |
| Block: 2135 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5810 | RingCT/type: yes/0 |
| Extra: 011096a9ea6c8d907dd427d9d393afbec2bb7aed4aae210f43610b7dd6f1665c9d02090000000226697be300 | ||
1 output(s) for total of 35.041452695301 HMNY
| stealth address | amount | amount idx | tag |
| 00: 490f38c94b05c4427117a2556e5118720b18cf245f47d8767eeb8e51e58c2198 | 35.041452695301 | 2461 of 0 | <2e> |
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": 2195,
"vin": [ {
"gen": {
"height": 2135
}
}
],
"vout": [ {
"amount": 35041452695301,
"target": {
"tagged_key": {
"key": "490f38c94b05c4427117a2556e5118720b18cf245f47d8767eeb8e51e58c2198",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 16, 150, 169, 234, 108, 141, 144, 125, 212, 39, 217, 211, 147, 175, 190, 194, 187, 122, 237, 74, 174, 33, 15, 67, 97, 11, 125, 214, 241, 102, 92, 157, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}