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: f011b7feec6c2459f7f9bcec6f81108ca692c5481960a8bd3d99d7bc346d417a
Tx prefix hash: 41b6a0a336a64a1b069f0882ff34445958a334b92fc3d6b158eae286180b8ae8
Tx public key: afebf6a5937f5a5d78cf75334e02cc77d5ce8a6c6e7b169968d611aae5e90b07
| Timestamp: 1780073176 | Timestamp [UTC]: 2026-05-29 16:46:16 | Age [y:d:h:m:s]: 00:018:15:19:05 |
| Block: 4669 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 4076 | RingCT/type: yes/0 |
| Extra: 01afebf6a5937f5a5d78cf75334e02cc77d5ce8a6c6e7b169968d611aae5e90b0702090000000226697be300 | ||
1 output(s) for total of 34.872498060354 HMNY
| stealth address | amount | amount idx | tag |
| 00: 846bc72b17335909f6e6028747f3959b8754b6e5d44336938855a360fa4eeef2 | 34.872498060354 | 5864 of 0 | <85> |
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": 4729,
"vin": [ {
"gen": {
"height": 4669
}
}
],
"vout": [ {
"amount": 34872498060354,
"target": {
"tagged_key": {
"key": "846bc72b17335909f6e6028747f3959b8754b6e5d44336938855a360fa4eeef2",
"view_tag": "85"
}
}
}
],
"extra": [ 1, 175, 235, 246, 165, 147, 127, 90, 93, 120, 207, 117, 51, 78, 2, 204, 119, 213, 206, 138, 108, 110, 123, 22, 153, 104, 214, 17, 170, 229, 233, 11, 7, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}