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: 0e201a0b50a0ade338a2a1e539cbec284a0d204361df55b4fa92599fcd33d13f
Tx prefix hash: 7d58ef8bdcb6de8328017588804cedfd86a4b185b5043ae360b8009ddfcefe71
Tx public key: ca4694875b39b0fd6f79cecaa19e2310c0b79e71c1ad7fcbe58a6fd636df674f
| Timestamp: 1780005262 | Timestamp [UTC]: 2026-05-28 21:54:22 | Age [y:d:h:m:s]: 00:011:04:46:14 |
| Block: 4074 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3822 | RingCT/type: yes/0 |
| Extra: 01ca4694875b39b0fd6f79cecaa19e2310c0b79e71c1ad7fcbe58a6fd636df674f02090000000726697be300 | ||
1 output(s) for total of 34.912096400242 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1d5753f4b5881c5ffac83b5fe3997eee8c33df52a45f2f2e66b5cfdb135e8a4f | 34.912096400242 | 5056 of 0 | <bd> |
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": 4134,
"vin": [ {
"gen": {
"height": 4074
}
}
],
"vout": [ {
"amount": 34912096400242,
"target": {
"tagged_key": {
"key": "1d5753f4b5881c5ffac83b5fe3997eee8c33df52a45f2f2e66b5cfdb135e8a4f",
"view_tag": "bd"
}
}
}
],
"extra": [ 1, 202, 70, 148, 135, 91, 57, 176, 253, 111, 121, 206, 202, 161, 158, 35, 16, 192, 183, 158, 113, 193, 173, 127, 203, 229, 138, 111, 214, 54, 223, 103, 79, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}