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: 1c89bcdc770b683b8816a6594ba038905a3125d64cca4a877b6c3ee0c931b4e1
Tx prefix hash: 4245afec1a708743fecc071e935e69d7b0584c76028df672fc3f2fcbb08f9f57
Tx public key: 745f2d9b74d7122afd46e9736aa0d30081789902f974a89ce417fea7eb2278db
| Timestamp: 1780980178 | Timestamp [UTC]: 2026-06-09 04:42:58 | Age [y:d:h:m:s]: 00:000:04:17:01 |
| Block: 8014 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 332 | RingCT/type: yes/0 |
| Extra: 01745f2d9b74d7122afd46e9736aa0d30081789902f974a89ce417fea7eb2278db020900000001e49593ff00 | ||
1 output(s) for total of 34.650716724159 HMNY
| stealth address | amount | amount idx | tag |
| 00: b2f1737a7f3b3941f9ee79fdfe2716b99858b8835a9babbaaf9836d5fec36e80 | 34.650716724159 | 9936 of 0 | <20> |
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": 8074,
"vin": [ {
"gen": {
"height": 8014
}
}
],
"vout": [ {
"amount": 34650716724159,
"target": {
"tagged_key": {
"key": "b2f1737a7f3b3941f9ee79fdfe2716b99858b8835a9babbaaf9836d5fec36e80",
"view_tag": "20"
}
}
}
],
"extra": [ 1, 116, 95, 45, 155, 116, 215, 18, 42, 253, 70, 233, 115, 106, 160, 211, 0, 129, 120, 153, 2, 249, 116, 168, 156, 228, 23, 254, 167, 235, 34, 120, 219, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}