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: b0f3988e605a6eb25bf502daef5b41751713817cf0854fb8ba2c3b244d171b4a
Tx prefix hash: 6a217b6aff895aaaa66dfc0a3ebb7285b0653ed6e11c8714a813edb8636aa8aa
Tx public key: c533433a92ea7d7e4c2334a7c59ebb0a710589dd9778f0a9846edf9909f42cb3
| Timestamp: 1780054597 | Timestamp [UTC]: 2026-05-29 11:36:37 | Age [y:d:h:m:s]: 00:010:15:03:59 |
| Block: 4435 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3462 | RingCT/type: yes/0 |
| Extra: 01c533433a92ea7d7e4c2334a7c59ebb0a710589dd9778f0a9846edf9909f42cb302090000000626697be300 | ||
1 output(s) for total of 34.888065827733 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1ad4e0409aa98aff7421d8fee42e48f5e1a5118cd6c72aee16980aabce81d6b1 | 34.888065827733 | 5551 of 0 | <7c> |
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": 4495,
"vin": [ {
"gen": {
"height": 4435
}
}
],
"vout": [ {
"amount": 34888065827733,
"target": {
"tagged_key": {
"key": "1ad4e0409aa98aff7421d8fee42e48f5e1a5118cd6c72aee16980aabce81d6b1",
"view_tag": "7c"
}
}
}
],
"extra": [ 1, 197, 51, 67, 58, 146, 234, 125, 126, 76, 35, 52, 167, 197, 158, 187, 10, 113, 5, 137, 221, 151, 120, 240, 169, 132, 110, 223, 153, 9, 244, 44, 179, 2, 9, 0, 0, 0, 6, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}