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: e54c0e16496dc09a3cf08a397aca57ca6f711b478ec14c42fbfa8c3b37132229
Tx prefix hash: e79102c0eea48270c8310da189def787091dd46d8978507db517bc89766ad73d
Tx public key: e27c35c87b00feac7d8305b5b3093099afba4c5c8cd84c15c9d3026a9ee744aa
| Timestamp: 1780693087 | Timestamp [UTC]: 2026-06-05 20:58:07 | Age [y:d:h:m:s]: 00:003:04:37:50 |
| Block: 5841 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 2045 | RingCT/type: yes/0 |
| Extra: 01e27c35c87b00feac7d8305b5b3093099afba4c5c8cd84c15c9d3026a9ee744aa020900000001e49593ff00 | ||
1 output(s) for total of 34.794630629962 HMNY
| stealth address | amount | amount idx | tag |
| 00: 6744910a16fbb94658e5926dcca5525ddf4f73a9a8fecccba49a5ae689b249a6 | 34.794630629962 | 7298 of 0 | <48> |
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": 5901,
"vin": [ {
"gen": {
"height": 5841
}
}
],
"vout": [ {
"amount": 34794630629962,
"target": {
"tagged_key": {
"key": "6744910a16fbb94658e5926dcca5525ddf4f73a9a8fecccba49a5ae689b249a6",
"view_tag": "48"
}
}
}
],
"extra": [ 1, 226, 124, 53, 200, 123, 0, 254, 172, 125, 131, 5, 181, 179, 9, 48, 153, 175, 186, 76, 92, 140, 216, 76, 21, 201, 211, 2, 106, 158, 231, 68, 170, 2, 9, 0, 0, 0, 1, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}