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: fa1be7ae918817c3f66b611794be14d07c0268109d2b6afbc72b54201309879d
Tx prefix hash: 3183407c6b4ede5f8d2ee490e3837ff2ae4f29223bf27a3b0d61f34a5e617ea2
Tx public key: 468abffb781b074d92c13f080a46da6c252bdd9e9321f9c07e5371f9b5ceda80
| Timestamp: 1779962303 | Timestamp [UTC]: 2026-05-28 09:58:23 | Age [y:d:h:m:s]: 00:011:14:48:24 |
| Block: 3774 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4112 | RingCT/type: yes/0 |
| Extra: 01468abffb781b074d92c13f080a46da6c252bdd9e9321f9c07e5371f9b5ceda8002090000000426697be300 | ||
1 output(s) for total of 34.936998997622 HMNY
| stealth address | amount | amount idx | tag |
| 00: d69c1e91d4d149866c32e6001a1269132e4353db083cbadc8c510da9d580355a | 34.936998997622 | 4578 of 0 | <80> |
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": 3834,
"vin": [ {
"gen": {
"height": 3774
}
}
],
"vout": [ {
"amount": 34936998997622,
"target": {
"tagged_key": {
"key": "d69c1e91d4d149866c32e6001a1269132e4353db083cbadc8c510da9d580355a",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 70, 138, 191, 251, 120, 27, 7, 77, 146, 193, 63, 8, 10, 70, 218, 108, 37, 43, 221, 158, 147, 33, 249, 192, 126, 83, 113, 249, 181, 206, 218, 128, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}