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: 9a9e5c724c532a614cf28a4db942ab2cde201ac1c7a57f8ad96a60c1ab797420
Tx prefix hash: b1d2e2587a2464f020a827bf468d9b22d7f9da960138776b782664eaef3c0e66
Tx public key: 12a21492c80c1e6a6982c1a434e3f3bdefe9c95df6ca9a514475480404784e23
| Timestamp: 1779641516 | Timestamp [UTC]: 2026-05-24 16:51:56 | Age [y:d:h:m:s]: 00:015:09:57:52 |
| Block: 1340 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6560 | RingCT/type: yes/0 |
| Extra: 0112a21492c80c1e6a6982c1a434e3f3bdefe9c95df6ca9a514475480404784e23020900000001ba6d17be00 | ||
1 output(s) for total of 35.094627883892 HMNY
| stealth address | amount | amount idx | tag |
| 00: b3bc7a6a1c36f0db8354dd5a95f239ee4a33e2971fbe1f8dc5b15db8fd3f1c4e | 35.094627883892 | 1490 of 0 | <29> |
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": 1400,
"vin": [ {
"gen": {
"height": 1340
}
}
],
"vout": [ {
"amount": 35094627883892,
"target": {
"tagged_key": {
"key": "b3bc7a6a1c36f0db8354dd5a95f239ee4a33e2971fbe1f8dc5b15db8fd3f1c4e",
"view_tag": "29"
}
}
}
],
"extra": [ 1, 18, 162, 20, 146, 200, 12, 30, 106, 105, 130, 193, 164, 52, 227, 243, 189, 239, 233, 201, 93, 246, 202, 154, 81, 68, 117, 72, 4, 4, 120, 78, 35, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}