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: 58ca87063f09e06243661ac172b19a7078f841445a8d71e1caafa41fba4c48ce
Tx prefix hash: b4c92ccac5709de4f0cf2a559d3ba95b95d4e20bec9d806097c3a3cd6070c48a
Tx public key: 60591d4dcbdc6f360c5bc71aa91a9d6e7040163269758aa333f4378a63359b88
| Timestamp: 1780768438 | Timestamp [UTC]: 2026-06-06 17:53:58 | Age [y:d:h:m:s]: 00:002:08:46:38 |
| Block: 6643 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1254 | RingCT/type: yes/0 |
| Extra: 0160591d4dcbdc6f360c5bc71aa91a9d6e7040163269758aa333f4378a63359b88020900000003e49593ff00 | ||
1 output(s) for total of 34.741446143685 HMNY
| stealth address | amount | amount idx | tag |
| 00: 8da7bdef2891f9edcaaf81a514d33464e6a53954ab11b5f2f87637297e254f4a | 34.741446143685 | 8189 of 0 | <f4> |
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": 6703,
"vin": [ {
"gen": {
"height": 6643
}
}
],
"vout": [ {
"amount": 34741446143685,
"target": {
"tagged_key": {
"key": "8da7bdef2891f9edcaaf81a514d33464e6a53954ab11b5f2f87637297e254f4a",
"view_tag": "f4"
}
}
}
],
"extra": [ 1, 96, 89, 29, 77, 203, 220, 111, 54, 12, 91, 199, 26, 169, 26, 157, 110, 112, 64, 22, 50, 105, 117, 138, 163, 51, 244, 55, 138, 99, 53, 155, 136, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}