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: ce1271aa9400f2205b275de9d474f8bf307fa6b3f0906aba8c8fda118c0a88d3
Tx prefix hash: d1b2fca688f8f34e26dbb2eb4aaf8dce5062f741280b345c230a633945968081
Tx public key: ea12f30019a33d7150a7421668519fb591d9666203f5d7e716a7c80dce08faa0
| Timestamp: 1779844517 | Timestamp [UTC]: 2026-05-27 01:15:17 | Age [y:d:h:m:s]: 00:012:22:03:36 |
| Block: 2435 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5451 | RingCT/type: yes/0 |
| Extra: 01ea12f30019a33d7150a7421668519fb591d9666203f5d7e716a7c80dce08faa002090000000126697be300 | ||
1 output(s) for total of 35.021407531632 HMNY
| stealth address | amount | amount idx | tag |
| 00: adf78409c778345eddc5db9766ea3690f288fa8d12ac8c931cb5e6c36aed59f0 | 35.021407531632 | 2861 of 0 | <bf> |
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": 2495,
"vin": [ {
"gen": {
"height": 2435
}
}
],
"vout": [ {
"amount": 35021407531632,
"target": {
"tagged_key": {
"key": "adf78409c778345eddc5db9766ea3690f288fa8d12ac8c931cb5e6c36aed59f0",
"view_tag": "bf"
}
}
}
],
"extra": [ 1, 234, 18, 243, 0, 25, 163, 61, 113, 80, 167, 66, 22, 104, 81, 159, 181, 145, 217, 102, 98, 3, 245, 215, 231, 22, 167, 200, 13, 206, 8, 250, 160, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}