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: ff75f045838c3f55ef55c52126465c3931f0695089b97449a4a02b3e27cb68c2
Tx prefix hash: c119dfbdb78ec84477ac724df7fd84cf371d90d574fbda2d3bfc7e20586c019e
Tx public key: e5d0ece227776e8227041649540719531a2f4d1e1f8e7dff9e67ce6bc9e6ceaa
| Timestamp: 1780802198 | Timestamp [UTC]: 2026-06-07 03:16:38 | Age [y:d:h:m:s]: 00:001:22:19:19 |
| Block: 6859 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1027 | RingCT/type: yes/0 |
| Extra: 01e5d0ece227776e8227041649540719531a2f4d1e1f8e7dff9e67ce6bc9e6ceaa020900000001e49593ff00 | ||
1 output(s) for total of 34.727136043272 HMNY
| stealth address | amount | amount idx | tag |
| 00: a9d2ed0ae2d2241487c70bb3d928c8f7646cf2f9d536581425dc8f10d8b0932d | 34.727136043272 | 8467 of 0 | <42> |
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": 6919,
"vin": [ {
"gen": {
"height": 6859
}
}
],
"vout": [ {
"amount": 34727136043272,
"target": {
"tagged_key": {
"key": "a9d2ed0ae2d2241487c70bb3d928c8f7646cf2f9d536581425dc8f10d8b0932d",
"view_tag": "42"
}
}
}
],
"extra": [ 1, 229, 208, 236, 226, 39, 119, 110, 130, 39, 4, 22, 73, 84, 7, 25, 83, 26, 47, 77, 30, 31, 142, 125, 255, 158, 103, 206, 107, 201, 230, 206, 170, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}