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: c0ef413366422eeec5d9432b75ce20ce0f5d0eec38a51ebfbc963ebcdddf359f
Tx prefix hash: 3f6c7a2a2d6000ae7f3b9f8076dd3e7307a7c9c7eef0b65be44182d41543049d
Tx public key: 41045e0a5f67420d9c51fc7f9a7f79b4ca2106e1dc3df2ce172a75272e4b2623
| Timestamp: 1779796505 | Timestamp [UTC]: 2026-05-26 11:55:05 | Age [y:d:h:m:s]: 00:021:20:34:07 |
| Block: 2271 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6474 | RingCT/type: yes/0 |
| Extra: 0141045e0a5f67420d9c51fc7f9a7f79b4ca2106e1dc3df2ce172a75272e4b262302090000000226697be300 | ||
1 output(s) for total of 35.032364133171 HMNY
| stealth address | amount | amount idx | tag |
| 00: 33c9ca9d997ef92b4c9be6080e97fb5afe973dabcb3a5df5a61d00319dd73247 | 35.032364133171 | 2641 of 0 | <2e> |
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": 2331,
"vin": [ {
"gen": {
"height": 2271
}
}
],
"vout": [ {
"amount": 35032364133171,
"target": {
"tagged_key": {
"key": "33c9ca9d997ef92b4c9be6080e97fb5afe973dabcb3a5df5a61d00319dd73247",
"view_tag": "2e"
}
}
}
],
"extra": [ 1, 65, 4, 94, 10, 95, 103, 66, 13, 156, 81, 252, 127, 154, 127, 121, 180, 202, 33, 6, 225, 220, 61, 242, 206, 23, 42, 117, 39, 46, 75, 38, 35, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}