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: 4aa4d59a885e2c118bbcb076ed7d69ece07e4e17d0b83d0f73e67cafc0455aa5
Tx prefix hash: bb16984d62fcc27fbd640b627255f919103890f151322892e5acfb2e0ebf7ab6
Tx public key: 0b3d0094cb776e6bb3c29f59ad40974da9e7ff76dfc295a38239e0ba4638d784
| Timestamp: 1779796063 | Timestamp [UTC]: 2026-05-26 11:47:43 | Age [y:d:h:m:s]: 00:013:16:45:19 |
| Block: 2268 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5747 | RingCT/type: yes/0 |
| Extra: 010b3d0094cb776e6bb3c29f59ad40974da9e7ff76dfc295a38239e0ba4638d78402090000000126697be300 | ||
1 output(s) for total of 35.032564590732 HMNY
| stealth address | amount | amount idx | tag |
| 00: c056fbf5b0bb9ecfec088a528760082aaa29891d5b6a6036a56eac43a61d5d25 | 35.032564590732 | 2636 of 0 | <0a> |
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": 2328,
"vin": [ {
"gen": {
"height": 2268
}
}
],
"vout": [ {
"amount": 35032564590732,
"target": {
"tagged_key": {
"key": "c056fbf5b0bb9ecfec088a528760082aaa29891d5b6a6036a56eac43a61d5d25",
"view_tag": "0a"
}
}
}
],
"extra": [ 1, 11, 61, 0, 148, 203, 119, 110, 107, 179, 194, 159, 89, 173, 64, 151, 77, 169, 231, 255, 118, 223, 194, 149, 163, 130, 57, 224, 186, 70, 56, 215, 132, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}