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: ff85d92d760a7fbd0ae0396eff2c2794ccb4c389cd11b97b03cca494efa4e532
Tx prefix hash: 5836889799090277720e2cff86c268d3536aef4708aa3712d566946ef10d03b4
Tx public key: 561376b9d53b28d0903bffcc8f1d41b93bc93608bb112803453e05aa0b60a659
| Timestamp: 1779952840 | Timestamp [UTC]: 2026-05-28 07:20:40 | Age [y:d:h:m:s]: 00:016:03:41:36 |
| Block: 3645 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5100 | RingCT/type: yes/0 |
| Extra: 01561376b9d53b28d0903bffcc8f1d41b93bc93608bb112803453e05aa0b60a65902090000000126697be300 | ||
1 output(s) for total of 34.940675030547 HMNY
| stealth address | amount | amount idx | tag |
| 00: 546ceb573348d3df97ce3dd80e8c32226d485fac683a4c0394f1aaa81e49bf50 | 34.940675030547 | 4405 of 0 | <f0> |
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": 3705,
"vin": [ {
"gen": {
"height": 3645
}
}
],
"vout": [ {
"amount": 34940675030547,
"target": {
"tagged_key": {
"key": "546ceb573348d3df97ce3dd80e8c32226d485fac683a4c0394f1aaa81e49bf50",
"view_tag": "f0"
}
}
}
],
"extra": [ 1, 86, 19, 118, 185, 213, 59, 40, 208, 144, 59, 255, 204, 143, 29, 65, 185, 59, 201, 54, 8, 187, 17, 40, 3, 69, 62, 5, 170, 11, 96, 166, 89, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}