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: a813bb772bdcf012f21c44ed7da418b067775a4130d9e9ea49c788f73d5069b0
Tx prefix hash: 4b59c7ccc5116552ca9af244c1442c95b3890e8bdb4d58c38bd961ddde21a723
Tx public key: 4ae8efa243385b4bc267867f69e4a9ddf89eb61e5f041a5ea3522760e4f67d8c
| Timestamp: 1780780361 | Timestamp [UTC]: 2026-06-06 21:12:41 | Age [y:d:h:m:s]: 00:006:13:49:35 |
| Block: 6760 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1985 | RingCT/type: yes/0 |
| Extra: 014ae8efa243385b4bc267867f69e4a9ddf89eb61e5f041a5ea3522760e4f67d8c020900000001e49593ff00 | ||
1 output(s) for total of 34.733694107468 HMNY
| stealth address | amount | amount idx | tag |
| 00: e7c4452708b4874b04d8943c7b8d8ef3a1816e58fa41b7852d2fc140e323f15d | 34.733694107468 | 8344 of 0 | <2a> |
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": 6820,
"vin": [ {
"gen": {
"height": 6760
}
}
],
"vout": [ {
"amount": 34733694107468,
"target": {
"tagged_key": {
"key": "e7c4452708b4874b04d8943c7b8d8ef3a1816e58fa41b7852d2fc140e323f15d",
"view_tag": "2a"
}
}
}
],
"extra": [ 1, 74, 232, 239, 162, 67, 56, 91, 75, 194, 103, 134, 127, 105, 228, 169, 221, 248, 158, 182, 30, 95, 4, 26, 94, 163, 82, 39, 96, 228, 246, 125, 140, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}