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: 3f389287f58ce3079155221e56b5ec943056dddd84a4bc2f5b9129b90dc70a60
Tx prefix hash: 0384faf4b508f75ab62cdb5e060cc5dfa063f43d825ac7f73592da944a33e033
Tx public key: c21f8fccb25b2abea318ae0d32eb7fd1b04eecdb0372f3695c7dbaaf679c792c
| Timestamp: 1779433560 | Timestamp [UTC]: 2026-05-22 07:06:00 | Age [y:d:h:m:s]: 00:017:19:34:36 |
| Block: 40 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0908 kB |
| Tx version: 2 | No of confirmations: 7857 | RingCT/type: yes/0 |
| Extra: 01c21f8fccb25b2abea318ae0d32eb7fd1b04eecdb0372f3695c7dbaaf679c792c020900000001a662ed0300 | ||
1 output(s) for total of 35.181754938095 HMNY
| stealth address | amount | amount idx | tag |
| 00: b5ec77a496945edb3e60cfeac4f2b442f3da7a25f3a42e2ff484fb31dac9efa2 | 35.181754938095 | 36 of 0 | <7b> |
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": 100,
"vin": [ {
"gen": {
"height": 40
}
}
],
"vout": [ {
"amount": 35181754938095,
"target": {
"tagged_key": {
"key": "b5ec77a496945edb3e60cfeac4f2b442f3da7a25f3a42e2ff484fb31dac9efa2",
"view_tag": "7b"
}
}
}
],
"extra": [ 1, 194, 31, 143, 204, 178, 91, 42, 190, 163, 24, 174, 13, 50, 235, 127, 209, 176, 78, 236, 219, 3, 114, 243, 105, 92, 125, 186, 175, 103, 156, 121, 44, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}