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: 15443a95f80d08f54d06f37002f8c50e64485f2ca4577040a1f3694cdff11869
Tx prefix hash: eee86306d0c8835e50a49e025a492444d0894c1fd56a21a36b221db420749e26
Tx public key: 8fe4aae253ee44d45b9035f5e3666528786e594abc70dbea755d53e1e2a6bac8
| Timestamp: 1779804680 | Timestamp [UTC]: 2026-05-26 14:11:20 | Age [y:d:h:m:s]: 00:013:11:24:37 |
| Block: 2337 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5549 | RingCT/type: yes/0 |
| Extra: 018fe4aae253ee44d45b9035f5e3666528786e594abc70dbea755d53e1e2a6bac802090000000126697be300 | ||
1 output(s) for total of 35.027954357033 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4e88fdc65700119ebbfdbd13f0a124d3ffff019b26f927dcf86678b2a2accbfc | 35.027954357033 | 2735 of 0 | <9b> |
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": 2397,
"vin": [ {
"gen": {
"height": 2337
}
}
],
"vout": [ {
"amount": 35027954357033,
"target": {
"tagged_key": {
"key": "4e88fdc65700119ebbfdbd13f0a124d3ffff019b26f927dcf86678b2a2accbfc",
"view_tag": "9b"
}
}
}
],
"extra": [ 1, 143, 228, 170, 226, 83, 238, 68, 212, 91, 144, 53, 245, 227, 102, 101, 40, 120, 110, 89, 74, 188, 112, 219, 234, 117, 93, 83, 225, 226, 166, 186, 200, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}