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: d97d5088172ff56e6bf33f581a701b01b8132fff19244b335f963df100baf858
Tx prefix hash: 4d546e5e1aa15625321a54d2e7f751d0f2c84589b00964b3b98142381a90d9b0
Tx public key: 127af33d1caa4d47ce194e965a092f2a2eb8c0bd935d891a5c66bd5aa341f09b
| Timestamp: 1780084669 | Timestamp [UTC]: 2026-05-29 19:57:49 | Age [y:d:h:m:s]: 00:010:07:41:01 |
| Block: 4803 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3145 | RingCT/type: yes/0 |
| Extra: 01127af33d1caa4d47ce194e965a092f2a2eb8c0bd935d891a5c66bd5aa341f09b02090000000726697be300 | ||
1 output(s) for total of 34.863586313216 HMNY
| stealth address | amount | amount idx | tag |
| 00: 70f028f8b17dd029ede3c9a7817a49ca69e4f46ab67cd8418dd0675c5706cb8b | 34.863586313216 | 6038 of 0 | <ba> |
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": 4863,
"vin": [ {
"gen": {
"height": 4803
}
}
],
"vout": [ {
"amount": 34863586313216,
"target": {
"tagged_key": {
"key": "70f028f8b17dd029ede3c9a7817a49ca69e4f46ab67cd8418dd0675c5706cb8b",
"view_tag": "ba"
}
}
}
],
"extra": [ 1, 18, 122, 243, 61, 28, 170, 77, 71, 206, 25, 78, 150, 90, 9, 47, 42, 46, 184, 192, 189, 147, 93, 137, 26, 92, 102, 189, 90, 163, 65, 240, 155, 2, 9, 0, 0, 0, 7, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}