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: 39b6334ef1f69c93a644abb11ef1fc516ef4b60d9e1c85f62aa84a90ff14be6c
Tx prefix hash: a64ab8fa9fd750a61951ff1f2037ad857e66a1f33f07570e45b4ae3fdbcb3da1
Tx public key: 9a9fb56798aec9afc47b77a79f500ef879f7cc9e2f9d6814fa6095e65e15f34e
| Timestamp: 1780693870 | Timestamp [UTC]: 2026-06-05 21:11:10 | Age [y:d:h:m:s]: 00:009:15:28:59 |
| Block: 5905 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2840 | RingCT/type: yes/0 |
| Extra: 019a9fb56798aec9afc47b77a79f500ef879f7cc9e2f9d6814fa6095e65e15f34e020900000001e49593ff00 | ||
1 output(s) for total of 34.790383493707 HMNY
| stealth address | amount | amount idx | tag |
| 00: fdecdace112d5c8d2ba99ab51f37fba722da5b04b8b9c9a64c40ad31c00ff89a | 34.790383493707 | 7366 of 0 | <4e> |
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": 5965,
"vin": [ {
"gen": {
"height": 5905
}
}
],
"vout": [ {
"amount": 34790383493707,
"target": {
"tagged_key": {
"key": "fdecdace112d5c8d2ba99ab51f37fba722da5b04b8b9c9a64c40ad31c00ff89a",
"view_tag": "4e"
}
}
}
],
"extra": [ 1, 154, 159, 181, 103, 152, 174, 201, 175, 196, 123, 119, 167, 159, 80, 14, 248, 121, 247, 204, 158, 47, 157, 104, 20, 250, 96, 149, 230, 94, 21, 243, 78, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}