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: 1ff6d873316cc8fbe43a38171e4138a7611f7f77c9e31fce2ae128908cff52b1
Tx prefix hash: 4b04a5d2565e39429ef137f39b6f877598ed8dd8d76bfc0504474150e9a638da
Tx public key: 218f44c42a9f8738168aaa74f3adbd7e791a25e35bbda6b7ebac2f43a2757bf1
| Timestamp: 1780729384 | Timestamp [UTC]: 2026-06-06 07:03:04 | Age [y:d:h:m:s]: 00:002:18:32:53 |
| Block: 6302 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1584 | RingCT/type: yes/0 |
| Extra: 01218f44c42a9f8738168aaa74f3adbd7e791a25e35bbda6b7ebac2f43a2757bf1020900000004e49593ff00 | ||
1 output(s) for total of 34.764049556123 HMNY
| stealth address | amount | amount idx | tag |
| 00: 596a547883e4139cfc9648dcdfbf67efefbed211475c0fc3efc3dea402581b61 | 34.764049556123 | 7787 of 0 | <e3> |
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": 6362,
"vin": [ {
"gen": {
"height": 6302
}
}
],
"vout": [ {
"amount": 34764049556123,
"target": {
"tagged_key": {
"key": "596a547883e4139cfc9648dcdfbf67efefbed211475c0fc3efc3dea402581b61",
"view_tag": "e3"
}
}
}
],
"extra": [ 1, 33, 143, 68, 196, 42, 159, 135, 56, 22, 138, 170, 116, 243, 173, 189, 126, 121, 26, 37, 227, 91, 189, 166, 183, 235, 172, 47, 67, 162, 117, 123, 241, 2, 9, 0, 0, 0, 4, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}