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: 2da14a1a644ab74bd4d5f5a9e6f4d670b73ef3cd05276f0e75845e08f07649ab
Tx prefix hash: 3966b9055e7859cdab0171ff4f5b92f83c286c661292554355753da6ba403d56
Tx public key: 1c6a2f9813e163034a484d254bf4a9b18f120561aab37653d5bb9391df6c3bc0
| Timestamp: 1780843147 | Timestamp [UTC]: 2026-06-07 14:39:07 | Age [y:d:h:m:s]: 00:001:14:59:32 |
| Block: 7483 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 623 | RingCT/type: yes/0 |
| Extra: 011c6a2f9813e163034a484d254bf4a9b18f120561aab37653d5bb9391df6c3bc0020900000003e49593ff00 | ||
1 output(s) for total of 34.685828854961 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8bb5238a5b588016c6fa8ba627441dd0db1315898ebfd6df2d8680ee0e238e9d | 34.685828854961 | 9219 of 0 | <59> |
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": 7543,
"vin": [ {
"gen": {
"height": 7483
}
}
],
"vout": [ {
"amount": 34685828854961,
"target": {
"tagged_key": {
"key": "8bb5238a5b588016c6fa8ba627441dd0db1315898ebfd6df2d8680ee0e238e9d",
"view_tag": "59"
}
}
}
],
"extra": [ 1, 28, 106, 47, 152, 19, 225, 99, 3, 74, 72, 77, 37, 75, 244, 169, 177, 143, 18, 5, 97, 170, 179, 118, 83, 213, 187, 147, 145, 223, 108, 59, 192, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}