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: 4d33ff29d31efd677f903eb8d590a496a5fa0a5cc59f786fd3838cb3b65d1ee6
Tx prefix hash: 9f27e0b58dcb6ee040b053626d8c06f34bb8dfb6bf6c33be4f2971cfc074e53b
Tx public key: cf48fedf89316174ae14065c6e26411bff407f15c285c717fc9ac780f42c2145
| Timestamp: 1780696946 | Timestamp [UTC]: 2026-06-05 22:02:26 | Age [y:d:h:m:s]: 00:003:01:16:27 |
| Block: 6003 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1883 | RingCT/type: yes/0 |
| Extra: 01cf48fedf89316174ae14065c6e26411bff407f15c285c717fc9ac780f42c2145020900000001e49593ff00 | ||
1 output(s) for total of 34.783881070983 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8cfb59839bee01f3350fa4b85a0a7401b20ddaee403111ff9acab3ae35f398e4 | 34.783881070983 | 7470 of 0 | <f7> |
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": 6063,
"vin": [ {
"gen": {
"height": 6003
}
}
],
"vout": [ {
"amount": 34783881070983,
"target": {
"tagged_key": {
"key": "8cfb59839bee01f3350fa4b85a0a7401b20ddaee403111ff9acab3ae35f398e4",
"view_tag": "f7"
}
}
}
],
"extra": [ 1, 207, 72, 254, 223, 137, 49, 97, 116, 174, 20, 6, 92, 110, 38, 65, 27, 255, 64, 127, 21, 194, 133, 199, 23, 252, 154, 199, 128, 244, 44, 33, 69, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}