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: 14233760621d5e58fe0088313b5646029d25702956fc04f2a773d964d10e0755
Tx prefix hash: 2cfd47cc11ef3d9c7cb559279db47e5f4d443597ec66fe166a1a88c2a92e29c7
Tx public key: f7ac6ee437152c41a4571cd1f5402b142f8e4e51d775cfdbbcf3f66bdbfc4aca
| Timestamp: 1779859176 | Timestamp [UTC]: 2026-05-27 05:19:36 | Age [y:d:h:m:s]: 00:012:17:59:17 |
| Block: 2658 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5228 | RingCT/type: yes/0 |
| Extra: 01f7ac6ee437152c41a4571cd1f5402b142f8e4e51d775cfdbbcf3f66bdbfc4aca02090000000126697be300 | ||
1 output(s) for total of 35.016307923366 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6a98a405e727099dc7093945ebf95c707a996d3a96341a6cd72e38b12de8efbd | 35.016307923366 | 3132 of 0 | <b6> |
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": 2718,
"vin": [ {
"gen": {
"height": 2658
}
}
],
"vout": [ {
"amount": 35016307923366,
"target": {
"tagged_key": {
"key": "6a98a405e727099dc7093945ebf95c707a996d3a96341a6cd72e38b12de8efbd",
"view_tag": "b6"
}
}
}
],
"extra": [ 1, 247, 172, 110, 228, 55, 21, 44, 65, 164, 87, 28, 209, 245, 64, 43, 20, 47, 142, 78, 81, 215, 117, 207, 219, 188, 243, 246, 107, 219, 252, 74, 202, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}