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: 1934f067d8a0b721480132d3f50a5eb7ed032001c86d193f5661a987349c4b09
Tx prefix hash: 640164e5fa3a07056866335688eec2a63ec1900bb3a16d7942af15a175c811fe
Tx public key: a20a28e8a8b9ff22e92e1ca7b09516e816552582289a498d032e20f79e07474a
| Timestamp: 1780987489 | Timestamp [UTC]: 2026-06-09 06:44:49 | Age [y:d:h:m:s]: 00:000:08:04:06 |
| Block: 8171 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 471 | RingCT/type: yes/0 |
| Extra: 01a20a28e8a8b9ff22e92e1ca7b09516e816552582289a498d032e20f79e07474a020900000001e49593ff00 | ||
1 output(s) for total of 34.640341981165 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1984d262b118b5f7cca57a7baa25b91f52d5aa058fcee2f84d23b474cb848d11 | 34.640341981165 | 10117 of 0 | <6d> |
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": 8231,
"vin": [ {
"gen": {
"height": 8171
}
}
],
"vout": [ {
"amount": 34640341981165,
"target": {
"tagged_key": {
"key": "1984d262b118b5f7cca57a7baa25b91f52d5aa058fcee2f84d23b474cb848d11",
"view_tag": "6d"
}
}
}
],
"extra": [ 1, 162, 10, 40, 232, 168, 185, 255, 34, 233, 46, 28, 167, 176, 149, 22, 232, 22, 85, 37, 130, 40, 154, 73, 141, 3, 46, 32, 247, 158, 7, 71, 74, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}