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: daa10279a0ad612fd54ebc2241f4a371ab7011f3bef26bfd859bb2a2fcde663f
Tx prefix hash: fb9c83c7c0cbba4c64cf8642c6f7b82c68e7d5d5c88c5c1cd5b6bd653b655515
Tx public key: 7dc3e5b3368f1c34440dc7d26c1a012b57ff3773834bd03e50b35990e2beef07
| Timestamp: 1780701361 | Timestamp [UTC]: 2026-06-05 23:16:01 | Age [y:d:h:m:s]: 00:003:02:19:56 |
| Block: 6056 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1830 | RingCT/type: yes/0 |
| Extra: 017dc3e5b3368f1c34440dc7d26c1a012b57ff3773834bd03e50b35990e2beef07020900000001e49593ff00 | ||
1 output(s) for total of 34.780364960989 HMNY
| stealth address | amount | amount idx | tag |
| 00: d8cd0e0d88fd4ac33b00eacc0ba6fe3a1ce9fbbe339254fc815625f3fd9ef7f9 | 34.780364960989 | 7525 of 0 | <bf> |
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": 6116,
"vin": [ {
"gen": {
"height": 6056
}
}
],
"vout": [ {
"amount": 34780364960989,
"target": {
"tagged_key": {
"key": "d8cd0e0d88fd4ac33b00eacc0ba6fe3a1ce9fbbe339254fc815625f3fd9ef7f9",
"view_tag": "bf"
}
}
}
],
"extra": [ 1, 125, 195, 229, 179, 54, 143, 28, 52, 68, 13, 199, 210, 108, 26, 1, 43, 87, 255, 55, 115, 131, 75, 208, 62, 80, 179, 89, 144, 226, 190, 239, 7, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}