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: 80ea5b5cfbbe4d3b3f405e4840d553f456598f8b99a03172ff2ef48762b48ff9
Tx prefix hash: f94dd7a49986a022f4b28e125e6c584e5086282e2ea56c8c912d1328a2921e5c
Tx public key: bdc2aa74511441fa19073b4e4c42b8753c3e84fad6a1fe9dccbaefb0c022de81
| Timestamp: 1780990506 | Timestamp [UTC]: 2026-06-09 07:35:06 | Age [y:d:h:m:s]: 00:000:06:02:30 |
| Block: 8223 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 377 | RingCT/type: yes/0 |
| Extra: 01bdc2aa74511441fa19073b4e4c42b8753c3e84fad6a1fe9dccbaefb0c022de81020900000001e49593ff00 | ||
1 output(s) for total of 34.636906445399 HMNY
| stealth address | amount | amount idx | tag |
| 00: a6dec72d2587b613517474ba0b91e09d3e6a26881d0425e3ef30a01de7bf8237 | 34.636906445399 | 10179 of 0 | <a4> |
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": 8283,
"vin": [ {
"gen": {
"height": 8223
}
}
],
"vout": [ {
"amount": 34636906445399,
"target": {
"tagged_key": {
"key": "a6dec72d2587b613517474ba0b91e09d3e6a26881d0425e3ef30a01de7bf8237",
"view_tag": "a4"
}
}
}
],
"extra": [ 1, 189, 194, 170, 116, 81, 20, 65, 250, 25, 7, 59, 78, 76, 66, 184, 117, 60, 62, 132, 250, 214, 161, 254, 157, 204, 186, 239, 176, 192, 34, 222, 129, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}