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: 952c3eb6e25fe1fe44d39edcbf8dc37db1c7fa212ba4b42b3e35be1d49713fe6
Tx prefix hash: 168ad3126ed893e9bed82590d7616c323d6bad8d2c813bfccd06c9cc81330514
Tx public key: bf0cec9e10e4f2658c3b4485aea9e4bb84d805e51367faf825350f2dc9917525
| Timestamp: 1780760164 | Timestamp [UTC]: 2026-06-06 15:36:04 | Age [y:d:h:m:s]: 00:002:09:10:43 |
| Block: 6561 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1325 | RingCT/type: yes/0 |
| Extra: 01bf0cec9e10e4f2658c3b4485aea9e4bb84d805e51367faf825350f2dc9917525020900000003e49593ff00 | ||
1 output(s) for total of 34.746880225892 HMNY
| stealth address | amount | amount idx | tag |
| 00: 7f5e89ee7ff1ede7c559feb9b1857a94a23d568a8c34191f8e917dc47de2e651 | 34.746880225892 | 8079 of 0 | <20> |
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": 6621,
"vin": [ {
"gen": {
"height": 6561
}
}
],
"vout": [ {
"amount": 34746880225892,
"target": {
"tagged_key": {
"key": "7f5e89ee7ff1ede7c559feb9b1857a94a23d568a8c34191f8e917dc47de2e651",
"view_tag": "20"
}
}
}
],
"extra": [ 1, 191, 12, 236, 158, 16, 228, 242, 101, 140, 59, 68, 133, 174, 169, 228, 187, 132, 216, 5, 229, 19, 103, 250, 248, 37, 53, 15, 45, 201, 145, 117, 37, 2, 9, 0, 0, 0, 3, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}