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: 9d1e5ffe65e639ee7124affaf52a46a8ae49c6756e973a2ef3156e5a3daf384f
Tx prefix hash: ef8fb5ef89c4a353e15867f2adf6cdd8863dd847cae8c6f975cfe7f91f541438
Tx public key: 3e49dbb980f243809ceea07bc3a5c96b79e7a5021438078c65e34ea9d2745d5b
| Timestamp: 1779897548 | Timestamp [UTC]: 2026-05-27 15:59:08 | Age [y:d:h:m:s]: 00:012:09:36:49 |
| Block: 3115 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4771 | RingCT/type: yes/0 |
| Extra: 013e49dbb980f243809ceea07bc3a5c96b79e7a5021438078c65e34ea9d2745d5b02090000000226697be300 | ||
1 output(s) for total of 34.979428269202 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3c86ec8ff9cd931abceb0b838972c094652ff4e13d6c83ae9ef0ef39a9274b93 | 34.979428269202 | 3717 of 0 | <8e> |
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": 3175,
"vin": [ {
"gen": {
"height": 3115
}
}
],
"vout": [ {
"amount": 34979428269202,
"target": {
"tagged_key": {
"key": "3c86ec8ff9cd931abceb0b838972c094652ff4e13d6c83ae9ef0ef39a9274b93",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 62, 73, 219, 185, 128, 242, 67, 128, 156, 238, 160, 123, 195, 165, 201, 107, 121, 231, 165, 2, 20, 56, 7, 140, 101, 227, 78, 169, 210, 116, 93, 91, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}