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: 91ffa5670f9052907759139b8ff372135f5f9cbe68f01645fd6ddd06717bbbd4
Tx prefix hash: 34160efa3b07706b903f202f2ce1f15739e08f31b0c481bcd53235f28ba0cb00
Tx public key: 7bca605fcb976b79e35f6d9ed35f24061e68d5f74565d72a6f2d46acea5ad503
| Timestamp: 1780060572 | Timestamp [UTC]: 2026-05-29 13:16:12 | Age [y:d:h:m:s]: 00:010:11:30:35 |
| Block: 4513 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3373 | RingCT/type: yes/0 |
| Extra: 017bca605fcb976b79e35f6d9ed35f24061e68d5f74565d72a6f2d46acea5ad50302090000000426697be300 | ||
1 output(s) for total of 34.882875799898 HMNY
| stealth address | amount | amount idx | tag |
| 00: 778d8ed9b3ac81571deda1e50d49e555c23125643e8b4383d5941d8687bef5bb | 34.882875799898 | 5658 of 0 | <7d> |
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": 4573,
"vin": [ {
"gen": {
"height": 4513
}
}
],
"vout": [ {
"amount": 34882875799898,
"target": {
"tagged_key": {
"key": "778d8ed9b3ac81571deda1e50d49e555c23125643e8b4383d5941d8687bef5bb",
"view_tag": "7d"
}
}
}
],
"extra": [ 1, 123, 202, 96, 95, 203, 151, 107, 121, 227, 95, 109, 158, 211, 95, 36, 6, 30, 104, 213, 247, 69, 101, 215, 42, 111, 45, 70, 172, 234, 90, 213, 3, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}