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: 07bfdb74a93a00d22bf9d97816fc110d72607972d2e987bb3e3a91e4bf61bccb
Tx prefix hash: a5defa300a3126bc98eaa5933bbf1003dacdaad9aa69ba8aa0992f45bbf75d33
Tx public key: 8b2e7cc189e2be9fd0f0610fe7c386b78562ea34f5067568660832f1c1f14ab1
| Timestamp: 1781005871 | Timestamp [UTC]: 2026-06-09 11:51:11 | Age [y:d:h:m:s]: 00:006:02:40:28 |
| Block: 8540 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 205 | RingCT/type: yes/0 |
| Extra: 018b2e7cc189e2be9fd0f0610fe7c386b78562ea34f5067568660832f1c1f14ab1020900000001e49593ff00 | ||
1 output(s) for total of 34.630598259388 HMNY
| stealth address | amount | amount idx | tag |
| 00: e69ee8209c4673c122361e867d3b4e1cc45b3985936c01aab4265c91b17f9f3f | 34.630598259388 | 10546 of 0 | <23> |
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": 8600,
"vin": [ {
"gen": {
"height": 8540
}
}
],
"vout": [ {
"amount": 34630598259388,
"target": {
"tagged_key": {
"key": "e69ee8209c4673c122361e867d3b4e1cc45b3985936c01aab4265c91b17f9f3f",
"view_tag": "23"
}
}
}
],
"extra": [ 1, 139, 46, 124, 193, 137, 226, 190, 159, 208, 240, 97, 15, 231, 195, 134, 183, 133, 98, 234, 52, 245, 6, 117, 104, 102, 8, 50, 241, 193, 241, 74, 177, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}