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: e335692b76a96d7e2a53f9284b42eb9e76487a67789c3ccdf8159f11f6555134
Tx prefix hash: 1c72a38fb4c647492569deac531f5306e5b2edc9d2a44e1cb4a21011a3921fa3
Tx public key: a07927b794aa4abdaa7f4104c66b82858d441bdd3dfc683a40379e90fb16f29a
| Timestamp: 1780758448 | Timestamp [UTC]: 2026-06-06 15:07:28 | Age [y:d:h:m:s]: 00:002:11:42:20 |
| Block: 6551 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1369 | RingCT/type: yes/0 |
| Extra: 01a07927b794aa4abdaa7f4104c66b82858d441bdd3dfc683a40379e90fb16f29a020900000002e49593ff00 | ||
1 output(s) for total of 34.747542976989 HMNY
| stealth address | amount | amount idx | tag |
| 00: 74e64b06aa480048ab5111a23244153bb807e042dc3654b05c285b686b9836dc | 34.747542976989 | 8063 of 0 | <ff> |
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": 6611,
"vin": [ {
"gen": {
"height": 6551
}
}
],
"vout": [ {
"amount": 34747542976989,
"target": {
"tagged_key": {
"key": "74e64b06aa480048ab5111a23244153bb807e042dc3654b05c285b686b9836dc",
"view_tag": "ff"
}
}
}
],
"extra": [ 1, 160, 121, 39, 183, 148, 170, 74, 189, 170, 127, 65, 4, 198, 107, 130, 133, 141, 68, 27, 221, 61, 252, 104, 58, 64, 55, 158, 144, 251, 22, 242, 154, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}