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: c5bf01f7a31033ada0da83b7f942eb25921507b34a490bbcd5b7eaf92bb70a5f
Tx prefix hash: 63fdf2ad6d5f9bebde9bddd001dd14ad3d56311df44a243eaba3cb6178f00dd9
Tx public key: 0ece54e80fc062a75d41af80656afb189209a3720db45f2a5406ad8f2e9f0348
| Timestamp: 1780906566 | Timestamp [UTC]: 2026-06-08 08:16:06 | Age [y:d:h:m:s]: 00:000:11:52:05 |
| Block: 7872 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 14 | RingCT/type: yes/0 |
| Extra: 010ece54e80fc062a75d41af80656afb189209a3720db45f2a5406ad8f2e9f03480209000000014a728a4c00 | ||
1 output(s) for total of 34.660102925747 HMNY
| stealth address | amount | amount idx | tag |
| 00: 73354eda6e0d5c8227acc31056935c209eed9db1489488578e80cc04f1c882f9 | 34.660102925747 | 9760 of 0 | <f6> |
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": 7932,
"vin": [ {
"gen": {
"height": 7872
}
}
],
"vout": [ {
"amount": 34660102925747,
"target": {
"tagged_key": {
"key": "73354eda6e0d5c8227acc31056935c209eed9db1489488578e80cc04f1c882f9",
"view_tag": "f6"
}
}
}
],
"extra": [ 1, 14, 206, 84, 232, 15, 192, 98, 167, 93, 65, 175, 128, 101, 106, 251, 24, 146, 9, 163, 114, 13, 180, 95, 42, 84, 6, 173, 143, 46, 159, 3, 72, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}