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: 42844f2c393fcb863e1e0267c47f447e4f273fbe46b6a91cf203e8b0c899c274
Tx prefix hash: 4da4cd3c6f8abd66595aa841545b272cf4837ab0fdac8a06bf6271d3971abfb4
Tx public key: be03e3ac7c801b78068df734d2e3dba8a6df58ac269ab53b71233c5cb9818abe
| Timestamp: 1780758851 | Timestamp [UTC]: 2026-06-06 15:14:11 | Age [y:d:h:m:s]: 00:002:11:26:25 |
| Block: 6553 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1344 | RingCT/type: yes/0 |
| Extra: 01be03e3ac7c801b78068df734d2e3dba8a6df58ac269ab53b71233c5cb9818abe020900000001e49593ff00 | ||
1 output(s) for total of 34.747410425759 HMNY
| stealth address | amount | amount idx | tag |
| 00: ab9e75c6a91e37a89e953ca13e846404eed7137a06c72a584c3f5ddad946b30a | 34.747410425759 | 8067 of 0 | <5c> |
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": 6613,
"vin": [ {
"gen": {
"height": 6553
}
}
],
"vout": [ {
"amount": 34747410425759,
"target": {
"tagged_key": {
"key": "ab9e75c6a91e37a89e953ca13e846404eed7137a06c72a584c3f5ddad946b30a",
"view_tag": "5c"
}
}
}
],
"extra": [ 1, 190, 3, 227, 172, 124, 128, 27, 120, 6, 141, 247, 52, 210, 227, 219, 168, 166, 223, 88, 172, 38, 154, 181, 59, 113, 35, 60, 92, 185, 129, 138, 190, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}