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: bf355cd9da8d304b6695d7821f6f3b1150697f51e4344f6e7ee7cde29bd6ab9f
Tx prefix hash: 19b256a54abce0aa2a52a2538847bb68a5d0fd45f10e04a7ada4ba702846ff41
Tx public key: a0a67d9206caf00dc15366ecfc2a2cea2f1b3857c519b29b140b3aba70f55f18
| Timestamp: 1780399050 | Timestamp [UTC]: 2026-06-02 11:17:30 | Age [y:d:h:m:s]: 00:006:12:01:23 |
| Block: 5266 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2620 | RingCT/type: yes/0 |
| Extra: 01a0a67d9206caf00dc15366ecfc2a2cea2f1b3857c519b29b140b3aba70f55f1802090000000126697be300 | ||
1 output(s) for total of 34.832811757072 HMNY
| stealth address | amount | amount idx | tag |
| 00: a38f1f3282a7a57810480603d420f3c60b99f096d00c184d8375328d373c9e1a | 34.832811757072 | 6673 of 0 | <e9> |
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": 5326,
"vin": [ {
"gen": {
"height": 5266
}
}
],
"vout": [ {
"amount": 34832811757072,
"target": {
"tagged_key": {
"key": "a38f1f3282a7a57810480603d420f3c60b99f096d00c184d8375328d373c9e1a",
"view_tag": "e9"
}
}
}
],
"extra": [ 1, 160, 166, 125, 146, 6, 202, 240, 13, 193, 83, 102, 236, 252, 42, 44, 234, 47, 27, 56, 87, 197, 25, 178, 155, 20, 11, 58, 186, 112, 245, 95, 24, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}