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: 4f9184858416467a15829a4fe705f4e85d92882b92309d8f8550553ce512bf1e
Tx prefix hash: 44f61687297e5cd3670673aed8c5f2e28da67f752267d686b8570d4e938f3907
Tx public key: 906ac21eefed542931f37e86f31965e9c4397ff4bf128e908107c2e735e34122
| Timestamp: 1780895354 | Timestamp [UTC]: 2026-06-08 05:09:14 | Age [y:d:h:m:s]: 00:000:16:02:53 |
| Block: 7760 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 126 | RingCT/type: yes/0 |
| Extra: 01906ac21eefed542931f37e86f31965e9c4397ff4bf128e908107c2e735e341220209000000014a728a4c00 | ||
1 output(s) for total of 34.667507920512 HMNY
| stealth address | amount | amount idx | tag |
| 00: 64d6043da00f634e22e8494bf1c7d61b2547ee86135091f57f539291714c0f7e | 34.667507920512 | 9610 of 0 | <48> |
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": 7820,
"vin": [ {
"gen": {
"height": 7760
}
}
],
"vout": [ {
"amount": 34667507920512,
"target": {
"tagged_key": {
"key": "64d6043da00f634e22e8494bf1c7d61b2547ee86135091f57f539291714c0f7e",
"view_tag": "48"
}
}
}
],
"extra": [ 1, 144, 106, 194, 30, 239, 237, 84, 41, 49, 243, 126, 134, 243, 25, 101, 233, 196, 57, 127, 244, 191, 18, 142, 144, 129, 7, 194, 231, 53, 227, 65, 34, 2, 9, 0, 0, 0, 1, 74, 114, 138, 76, 0
],
"rct_signatures": {
"type": 0
}
}