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: fe768904a9bb4f4d317f7d5f372be8e5ef66d79b40940cb5d0520bd70dbaf534
Tx prefix hash: cf43d8ea947966dbaf49dcd29918207f66a014fc11353482bcce9622261f17a5
Tx public key: 8b873ac170e8065930d2c142d68d592d61a19644ca786b9a7dd67901105b41b2
| Timestamp: 1780998180 | Timestamp [UTC]: 2026-06-09 09:43:00 | Age [y:d:h:m:s]: 00:007:22:46:12 |
| Block: 8390 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 355 | RingCT/type: yes/0 |
| Extra: 018b873ac170e8065930d2c142d68d592d61a19644ca786b9a7dd67901105b41b2020900000001e49593ff00 | ||
1 output(s) for total of 34.625875394240 HMNY
| stealth address | amount | amount idx | tag |
| 00: b73a1d4c58f3a01b078cfdcf02b12fdc9418c91b84428fa73faa0e1602f26ff6 | 34.625875394240 | 10372 of 0 | <ea> |
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": 8450,
"vin": [ {
"gen": {
"height": 8390
}
}
],
"vout": [ {
"amount": 34625875394240,
"target": {
"tagged_key": {
"key": "b73a1d4c58f3a01b078cfdcf02b12fdc9418c91b84428fa73faa0e1602f26ff6",
"view_tag": "ea"
}
}
}
],
"extra": [ 1, 139, 135, 58, 193, 112, 232, 6, 89, 48, 210, 193, 66, 214, 141, 89, 45, 97, 161, 150, 68, 202, 120, 107, 154, 125, 214, 121, 1, 16, 91, 65, 178, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}