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: d185e289c2c50316b9dc45e1b9b18e6f8dce7e436cc32947eaf7a868e08941c2
Tx prefix hash: 5aa57154498cc77b8d708933c793d4548f04467707d1275f2c403c979b7671b0
Tx public key: 9304ff3345cbf27057af059474f8d7ced07145d71b895cb466642f1629c4f233
| Timestamp: 1779480757 | Timestamp [UTC]: 2026-05-22 20:12:37 | Age [y:d:h:m:s]: 00:017:06:27:59 |
| Block: 650 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7246 | RingCT/type: yes/0 |
| Extra: 019304ff3345cbf27057af059474f8d7ced07145d71b895cb466642f1629c4f23302090000000493369e7d00 | ||
1 output(s) for total of 35.140845340469 HMNY
| stealth address | amount | amount idx | tag |
| 00: 4487c52a3bde1454401f2d9c67e3f0cfd0ef221bc252836f575583eaa43ed5fe | 35.140845340469 | 693 of 0 | <2b> |
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": 710,
"vin": [ {
"gen": {
"height": 650
}
}
],
"vout": [ {
"amount": 35140845340469,
"target": {
"tagged_key": {
"key": "4487c52a3bde1454401f2d9c67e3f0cfd0ef221bc252836f575583eaa43ed5fe",
"view_tag": "2b"
}
}
}
],
"extra": [ 1, 147, 4, 255, 51, 69, 203, 242, 112, 87, 175, 5, 148, 116, 248, 215, 206, 208, 113, 69, 215, 27, 137, 92, 180, 102, 100, 47, 22, 41, 196, 242, 51, 2, 9, 0, 0, 0, 4, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}