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: baa53bfdc6a0d4f72c16d4df617d180ac538c2c94a0f81f6dd4bc9c5bb9556d3
Tx prefix hash: ba900e26cc08c4eac31fd5aaea335c95da470424cf38db0c37a448120f19a258
Tx public key: d69f324903e245c7beb6d56e7cfbc9b4ee8fa8d1b7d706381370db33f7a3fbb8
| Timestamp: 1780768118 | Timestamp [UTC]: 2026-06-06 17:48:38 | Age [y:d:h:m:s]: 00:002:06:58:09 |
| Block: 6638 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1248 | RingCT/type: yes/0 |
| Extra: 01d69f324903e245c7beb6d56e7cfbc9b4ee8fa8d1b7d706381370db33f7a3fbb8020900000002e49593ff00 | ||
1 output(s) for total of 34.741777465829 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8e05345c4c9cda3f05b9544ea8e71e61725c1a29f5b93cc31205fa10274375ae | 34.741777465829 | 8182 of 0 | <ca> |
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": 6698,
"vin": [ {
"gen": {
"height": 6638
}
}
],
"vout": [ {
"amount": 34741777465829,
"target": {
"tagged_key": {
"key": "8e05345c4c9cda3f05b9544ea8e71e61725c1a29f5b93cc31205fa10274375ae",
"view_tag": "ca"
}
}
}
],
"extra": [ 1, 214, 159, 50, 73, 3, 226, 69, 199, 190, 182, 213, 110, 124, 251, 201, 180, 238, 143, 168, 209, 183, 215, 6, 56, 19, 112, 219, 51, 247, 163, 251, 184, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}