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: 51f56adc0601a22300c5a5f5ffba45b8b16da1fcfee28160ce60a8064521061f
Tx prefix hash: 9971727f883c943d5be23e6b15e878810f91beecd5952004d4ee2df8215c3862
Tx public key: 14e0e583fa70417064a46ec54f5f9a4d09222ed0fdc0260b9c6a57c4be01ff5f
| Timestamp: 1779977108 | Timestamp [UTC]: 2026-05-28 14:05:08 | Age [y:d:h:m:s]: 00:011:09:13:45 |
| Block: 3893 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3993 | RingCT/type: yes/0 |
| Extra: 0114e0e583fa70417064a46ec54f5f9a4d09222ed0fdc0260b9c6a57c4be01ff5f02090000000326697be300 | ||
1 output(s) for total of 34.924151199078 HMNY
| stealth address | amount | amount idx | tag |
| 00: 740c370a98c8253599bb883a2e442dbf158d52e712016b3b39ceb0f6bcb2d8c3 | 34.924151199078 | 4768 of 0 | <01> |
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": 3953,
"vin": [ {
"gen": {
"height": 3893
}
}
],
"vout": [ {
"amount": 34924151199078,
"target": {
"tagged_key": {
"key": "740c370a98c8253599bb883a2e442dbf158d52e712016b3b39ceb0f6bcb2d8c3",
"view_tag": "01"
}
}
}
],
"extra": [ 1, 20, 224, 229, 131, 250, 112, 65, 112, 100, 164, 110, 197, 79, 95, 154, 77, 9, 34, 46, 208, 253, 192, 38, 11, 156, 106, 87, 196, 190, 1, 255, 95, 2, 9, 0, 0, 0, 3, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}