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: d70648daf240d453b0bc5530c6b4905d4601efda37a70e8b05e5e3c1d40a6cbe
Tx prefix hash: 01b3a8cb4ff3aff1377b7b2c7b0820ce81604b033ded1db14c936bc6a77c8e89
Tx public key: a87edaf9b37a2d97fc7f500ebe3041fc5a1403c10ffbb7b0e6e5ae9c07f12f88
| Timestamp: 1780694356 | Timestamp [UTC]: 2026-06-05 21:19:16 | Age [y:d:h:m:s]: 00:003:04:16:41 |
| Block: 5933 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1953 | RingCT/type: yes/0 |
| Extra: 01a87edaf9b37a2d97fc7f500ebe3041fc5a1403c10ffbb7b0e6e5ae9c07f12f88020900000001e49593ff00 | ||
1 output(s) for total of 34.788525534617 HMNY
| stealth address | amount | amount idx | tag |
| 00: e14bed82d9e126a37e33cf1e7c3eb69627462c3a3138153d9587ce0f0a1fb317 | 34.788525534617 | 7394 of 0 | <80> |
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": 5993,
"vin": [ {
"gen": {
"height": 5933
}
}
],
"vout": [ {
"amount": 34788525534617,
"target": {
"tagged_key": {
"key": "e14bed82d9e126a37e33cf1e7c3eb69627462c3a3138153d9587ce0f0a1fb317",
"view_tag": "80"
}
}
}
],
"extra": [ 1, 168, 126, 218, 249, 179, 122, 45, 151, 252, 127, 80, 14, 190, 48, 65, 252, 90, 20, 3, 193, 15, 251, 183, 176, 230, 229, 174, 156, 7, 241, 47, 136, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}