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: db3db624fc1bbf9e833c9b1c61d1887e92c6695a9c12500fbdb92ce693878f95
Tx prefix hash: 071e389169698f2a7f77958a3697ec8c0ac5c158bba08ee9bd93ed57a1a3511d
Tx public key: e1d614f040f3e16dc578c0fa94c8210a201d87a8c302c8f7e85aa27a2ac54331
| Timestamp: 1779963339 | Timestamp [UTC]: 2026-05-28 10:15:39 | Age [y:d:h:m:s]: 00:011:15:20:18 |
| Block: 3784 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4102 | RingCT/type: yes/0 |
| Extra: 01e1d614f040f3e16dc578c0fa94c8210a201d87a8c302c8f7e85aa27a2ac5433102090000000526697be300 | ||
1 output(s) for total of 34.931412726809 HMNY
| stealth address | amount | amount idx | tag |
| 00: 5d0f07cedc529e8d7790644cbc0beaf88098523744cf4b7d316cdf718ecddd21 | 34.931412726809 | 4594 of 0 | <85> |
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": 3844,
"vin": [ {
"gen": {
"height": 3784
}
}
],
"vout": [ {
"amount": 34931412726809,
"target": {
"tagged_key": {
"key": "5d0f07cedc529e8d7790644cbc0beaf88098523744cf4b7d316cdf718ecddd21",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 225, 214, 20, 240, 64, 243, 225, 109, 197, 120, 192, 250, 148, 200, 33, 10, 32, 29, 135, 168, 195, 2, 200, 247, 232, 90, 162, 122, 42, 197, 67, 49, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}