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: a0f92d1c7aa82a00d7c6eaab3f77f75c3de8351630592059aa1218ec6804fdec
Tx prefix hash: e064f6308f4758e347d16bdc333659e2daab6e6538dd47ba8bb5dca3577b71f9
Tx public key: 8ecfe667f55635d4bcc1d0841dceea87172a6756c792fc639ea42352e4c9a295
| Timestamp: 1780694629 | Timestamp [UTC]: 2026-06-05 21:23:49 | Age [y:d:h:m:s]: 00:003:01:55:04 |
| Block: 5952 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1934 | RingCT/type: yes/0 |
| Extra: 018ecfe667f55635d4bcc1d0841dceea87172a6756c792fc639ea42352e4c9a295020900000001e49593ff00 | ||
1 output(s) for total of 34.787264833173 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2b9de87d1a5d60995bc54247f24276e506462f320e6fe725a649ef150e127066 | 34.787264833173 | 7415 of 0 | <8e> |
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": 6012,
"vin": [ {
"gen": {
"height": 5952
}
}
],
"vout": [ {
"amount": 34787264833173,
"target": {
"tagged_key": {
"key": "2b9de87d1a5d60995bc54247f24276e506462f320e6fe725a649ef150e127066",
"view_tag": "8e"
}
}
}
],
"extra": [ 1, 142, 207, 230, 103, 245, 86, 53, 212, 188, 193, 208, 132, 29, 206, 234, 135, 23, 42, 103, 86, 199, 146, 252, 99, 158, 164, 35, 82, 228, 201, 162, 149, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}