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: 80f4e655c55495746efdaa5434cef922e8074d3c5ab60fcda1be0a7259c86ccf
Tx prefix hash: 253fbbda2e56089e74cd8d1d374a9ebcc02727377402a215acf3a39130cef6f2
Tx public key: 8e572df6f0599f5cb912c771c312da03640cb87c73599a7cc196c52bf938515f
| Timestamp: 1779712537 | Timestamp [UTC]: 2026-05-25 12:35:37 | Age [y:d:h:m:s]: 00:018:22:26:39 |
| Block: 1589 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7156 | RingCT/type: yes/0 |
| Extra: 018e572df6f0599f5cb912c771c312da03640cb87c73599a7cc196c52bf938515f020900000007ba6d17be00 | ||
1 output(s) for total of 35.077964340383 HMNY
| stealth address | amount | amount idx | tag |
| 00: 63dcd0895f26389b0073950204b1117dcb3740603803d2d6a0e164cd33272107 | 35.077964340383 | 1747 of 0 | <b7> |
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": 1649,
"vin": [ {
"gen": {
"height": 1589
}
}
],
"vout": [ {
"amount": 35077964340383,
"target": {
"tagged_key": {
"key": "63dcd0895f26389b0073950204b1117dcb3740603803d2d6a0e164cd33272107",
"view_tag": "b7"
}
}
}
],
"extra": [ 1, 142, 87, 45, 246, 240, 89, 159, 92, 185, 18, 199, 113, 195, 18, 218, 3, 100, 12, 184, 124, 115, 89, 154, 124, 193, 150, 197, 43, 249, 56, 81, 95, 2, 9, 0, 0, 0, 7, 186, 109, 23, 190, 0
],
"rct_signatures": {
"type": 0
}
}