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: 90d177629f4532a7e2c7d1d78acef791e8ba88e3362502d28a4193260690af62
Tx prefix hash: 9c6807935664e113c0ed41fb7b762145c6e7baebe01e19ed029039786bdeff8b
Tx public key: b776d58d99564c8b56395ac866b67b352887ccde769fb9cd7a8aefa858aae7a0
| Timestamp: 1779640202 | Timestamp [UTC]: 2026-05-24 16:30:02 | Age [y:d:h:m:s]: 00:015:12:03:00 |
| Block: 1283 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6749 | RingCT/type: yes/0 |
| Extra: 01b776d58d99564c8b56395ac866b67b352887ccde769fb9cd7a8aefa858aae7a0020900000001ba6d17be00 | ||
1 output(s) for total of 35.098443543304 HMNY
| stealth address | amount | amount idx | tag |
| 00: 03cdd1f22fa5c846aeb24c4ebb2b1352f266b65b8aab7ca07962bf556c3826cb | 35.098443543304 | 1431 of 0 | <5d> |
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": 1343,
"vin": [ {
"gen": {
"height": 1283
}
}
],
"vout": [ {
"amount": 35098443543304,
"target": {
"tagged_key": {
"key": "03cdd1f22fa5c846aeb24c4ebb2b1352f266b65b8aab7ca07962bf556c3826cb",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 183, 118, 213, 141, 153, 86, 76, 139, 86, 57, 90, 200, 102, 182, 123, 53, 40, 135, 204, 222, 118, 159, 185, 205, 122, 138, 239, 168, 88, 170, 231, 160, 2, 9, 0, 0, 0, 1, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}