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: dc4e9bc7f5f0061d30eb4c1bb6b4784f653e8b5285bfd32cfd55fe95638e1c4c
Tx prefix hash: df8d6e8ad507a81d88bb76a076edb8d15c981350756bdeb0143ba1726969702a
Tx public key: a02333ed88323377c7d4c3921e708dc5793321f590d65fc8c2688c552459c9dc
| Timestamp: 1779800018 | Timestamp [UTC]: 2026-05-26 12:53:38 | Age [y:d:h:m:s]: 00:021:19:28:41 |
| Block: 2297 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 6448 | RingCT/type: yes/0 |
| Extra: 01a02333ed88323377c7d4c3921e708dc5793321f590d65fc8c2688c552459c9dc02090000000426697be300 | ||
1 output(s) for total of 35.030626882363 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8279d1a63da19923738e6067c24412f725003d9d5a0fedf928a39d9bfde464c0 | 35.030626882363 | 2679 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": 2357,
"vin": [ {
"gen": {
"height": 2297
}
}
],
"vout": [ {
"amount": 35030626882363,
"target": {
"tagged_key": {
"key": "8279d1a63da19923738e6067c24412f725003d9d5a0fedf928a39d9bfde464c0",
"view_tag": "5d"
}
}
}
],
"extra": [ 1, 160, 35, 51, 237, 136, 50, 51, 119, 199, 212, 195, 146, 30, 112, 141, 197, 121, 51, 33, 245, 144, 214, 95, 200, 194, 104, 140, 85, 36, 89, 201, 220, 2, 9, 0, 0, 0, 4, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}