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: b9b704da26087ad46f2edaa36c88af86419f3e508c39d32b397ba630186a9a4b
Tx prefix hash: 186a6157bac1a860b4f10e59d7083cafab668cfc5fc39821468c5e8483745531
Tx public key: a0e5024fb33b978aa06b645ffc373ac47f24347624a84865822546f58ab60ec6
| Timestamp: 1780900458 | Timestamp [UTC]: 2026-06-08 06:34:18 | Age [y:d:h:m:s]: 00:000:19:01:39 |
| Block: 7809 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 77 | RingCT/type: yes/0 |
| Extra: 01a0e5024fb33b978aa06b645ffc373ac47f24347624a84865822546f58ab60ec60209000000034a728a4c00 | ||
1 output(s) for total of 34.664268040656 HMNY
| stealth address | amount | amount idx | tag |
| 00: c2def2d637cca8d24969f55eeb8cb8f9ad8291e9f63f8d41708fc848f4440bf5 | 34.664268040656 | 9679 of 0 | <d4> |
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": 7869,
"vin": [ {
"gen": {
"height": 7809
}
}
],
"vout": [ {
"amount": 34664268040656,
"target": {
"tagged_key": {
"key": "c2def2d637cca8d24969f55eeb8cb8f9ad8291e9f63f8d41708fc848f4440bf5",
"view_tag": "d4"
}
}
}
],
"extra": [ 1, 160, 229, 2, 79, 179, 59, 151, 138, 160, 107, 100, 95, 252, 55, 58, 196, 127, 36, 52, 118, 36, 168, 72, 101, 130, 37, 70, 245, 138, 182, 14, 198, 2, 9, 0, 0, 0, 3, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}