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: c4eaaa700e7954b886d82d3b0068ddf336dcd96562224e06739a3e4be95c21c5
Tx prefix hash: a35687c06e4d39887c3473a04cc22ddcbb224e7d243712a7d808d9cc6230851e
Tx public key: e8abd2691553ebc706c8d5d3e75ff88aa3e39aa385c69071d528451fa0959101
| Timestamp: 1779892988 | Timestamp [UTC]: 2026-05-27 14:43:08 | Age [y:d:h:m:s]: 00:012:10:52:49 |
| Block: 3076 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4810 | RingCT/type: yes/0 |
| Extra: 01e8abd2691553ebc706c8d5d3e75ff88aa3e39aa385c69071d528451fa095910102090000000426697be300 | ||
1 output(s) for total of 34.978616115121 HMNY
| stealth address | amount | amount idx | tag |
| 00: cd7d79cd82df5f8e4a9d8393f166e902d67bfda9f0a8ca73d2d74b0e69483170 | 34.978616115121 | 3664 of 0 | <5e> |
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": 3136,
"vin": [ {
"gen": {
"height": 3076
}
}
],
"vout": [ {
"amount": 34978616115121,
"target": {
"tagged_key": {
"key": "cd7d79cd82df5f8e4a9d8393f166e902d67bfda9f0a8ca73d2d74b0e69483170",
"view_tag": "5e"
}
}
}
],
"extra": [ 1, 232, 171, 210, 105, 21, 83, 235, 199, 6, 200, 213, 211, 231, 95, 248, 138, 163, 227, 154, 163, 133, 198, 144, 113, 213, 40, 69, 31, 160, 149, 145, 1, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}