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: 852507841a9156206edbc9187c73ba870181a25236e1b0c8ffea2096370b5cc7
Tx prefix hash: ebd888110f766dff0fc1199e112d479f14976e79231e49748246d294aec66b06
Tx public key: e60c5b445c752fcd5bba53e02fa4cd08d24fd2981c47a326f6ded23d9383a158
| Timestamp: 1779780426 | Timestamp [UTC]: 2026-05-26 07:27:06 | Age [y:d:h:m:s]: 00:013:15:51:47 |
| Block: 2096 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5790 | RingCT/type: yes/0 |
| Extra: 01e60c5b445c752fcd5bba53e02fa4cd08d24fd2981c47a326f6ded23d9383a15802090000000126697be300 | ||
1 output(s) for total of 35.044059409147 HMNY
| stealth address | amount | amount idx | tag |
| 00: bbecff15f3e2f1e74053cda06f4f878ce98f19f374ae82e2c34897b78edc6fdf | 35.044059409147 | 2412 of 0 | <de> |
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": 2156,
"vin": [ {
"gen": {
"height": 2096
}
}
],
"vout": [ {
"amount": 35044059409147,
"target": {
"tagged_key": {
"key": "bbecff15f3e2f1e74053cda06f4f878ce98f19f374ae82e2c34897b78edc6fdf",
"view_tag": "de"
}
}
}
],
"extra": [ 1, 230, 12, 91, 68, 92, 117, 47, 205, 91, 186, 83, 224, 47, 164, 205, 8, 210, 79, 210, 152, 28, 71, 163, 38, 246, 222, 210, 61, 147, 131, 161, 88, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}