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: 0fbd9118d8434943bfce9e2f0ea2f5f30feea1b70b808dcdcacf03d5b40df8b2
Tx prefix hash: accdc80ba9c6fffd71cfd7240045754ca09a012e7f54a1d1bc68a0636be7d3c3
Tx public key: 6d33ef58a698e1c0d6d7cdecb7c24b025ab50f24864daf23242428d1a0a95c1a
| Timestamp: 1779438161 | Timestamp [UTC]: 2026-05-22 08:22:41 | Age [y:d:h:m:s]: 00:017:17:13:16 |
| Block: 183 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7703 | RingCT/type: yes/0 |
| Extra: 016d33ef58a698e1c0d6d7cdecb7c24b025ab50f24864daf23242428d1a0a95c1a0209000000015cddc08000 | ||
1 output(s) for total of 35.172160383744 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6751130359d551bc367d5112d06b6de9f9ffd192a4417b5865cc92d0a8dd9fbd | 35.172160383744 | 179 of 0 | <b5> |
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": 243,
"vin": [ {
"gen": {
"height": 183
}
}
],
"vout": [ {
"amount": 35172160383744,
"target": {
"tagged_key": {
"key": "6751130359d551bc367d5112d06b6de9f9ffd192a4417b5865cc92d0a8dd9fbd",
"view_tag": "b5"
}
}
}
],
"extra": [ 1, 109, 51, 239, 88, 166, 152, 225, 192, 214, 215, 205, 236, 183, 194, 75, 2, 90, 181, 15, 36, 134, 77, 175, 35, 36, 36, 40, 209, 160, 169, 92, 26, 2, 9, 0, 0, 0, 1, 92, 221, 192, 128, 0
],
"rct_signatures": {
"type": 0
}
}