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: 23ff9db65178673b24d43f4f356e29654e0ee280e57f834f0b54bcc70e1bb364
Tx prefix hash: b2c9ef3093004e72811e4f3a428225b6268f314a39d898af929ab3fb889160c6
Tx public key: 824c41b08fd3fae82addab20e086357b03933ca898c794eaacd27706601cdea1
| Timestamp: 1780116294 | Timestamp [UTC]: 2026-05-30 04:44:54 | Age [y:d:h:m:s]: 00:014:06:17:22 |
| Block: 4878 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3867 | RingCT/type: yes/0 |
| Extra: 01824c41b08fd3fae82addab20e086357b03933ca898c794eaacd27706601cdea102090000000526697be300 | ||
1 output(s) for total of 34.858599389135 HMNY
| stealth address | amount | amount idx | tag |
| 00: 3d028a3262991a67eaa5e4e0f6fab554157d0fa9d5c46bced027c98daa819da1 | 34.858599389135 | 6168 of 0 | <15> |
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": 4938,
"vin": [ {
"gen": {
"height": 4878
}
}
],
"vout": [ {
"amount": 34858599389135,
"target": {
"tagged_key": {
"key": "3d028a3262991a67eaa5e4e0f6fab554157d0fa9d5c46bced027c98daa819da1",
"view_tag": "15"
}
}
}
],
"extra": [ 1, 130, 76, 65, 176, 143, 211, 250, 232, 42, 221, 171, 32, 224, 134, 53, 123, 3, 147, 60, 168, 152, 199, 148, 234, 172, 210, 119, 6, 96, 28, 222, 161, 2, 9, 0, 0, 0, 5, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}