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: 1772e0e82bcb58b7df239f7c9de575c3ffbed26518857ed31863d15339bbc9a1
Tx prefix hash: cfeb7d263ea24db96f9188594c74d8e6d467ee9e0f60bc979446600a8afb38e4
Tx public key: c1bc551d3ccdf3cd0718eb78f1ac34e5a74143b0d335fbfc9d6f4f5f8677f57c
| Timestamp: 1779900727 | Timestamp [UTC]: 2026-05-27 16:52:07 | Age [y:d:h:m:s]: 00:012:08:43:50 |
| Block: 3140 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4746 | RingCT/type: yes/0 |
| Extra: 01c1bc551d3ccdf3cd0718eb78f1ac34e5a74143b0d335fbfc9d6f4f5f8677f57c02090000000226697be300 | ||
1 output(s) for total of 34.974346521049 HMNY
| stealth address | amount | amount idx | tag |
| 00: eb9a984136fcf995d08d9f9828a5c03dd4341ccff520fa957f5a5207a1677904 | 34.974346521049 | 3754 of 0 | <32> |
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": 3200,
"vin": [ {
"gen": {
"height": 3140
}
}
],
"vout": [ {
"amount": 34974346521049,
"target": {
"tagged_key": {
"key": "eb9a984136fcf995d08d9f9828a5c03dd4341ccff520fa957f5a5207a1677904",
"view_tag": "32"
}
}
}
],
"extra": [ 1, 193, 188, 85, 29, 60, 205, 243, 205, 7, 24, 235, 120, 241, 172, 52, 229, 167, 65, 67, 176, 211, 53, 251, 252, 157, 111, 79, 95, 134, 119, 245, 124, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}