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: 9d98b49a0ab917893bb75498bde417a9b8d9359363cb608e32aa1d0b4fd3bb2d
Tx prefix hash: b6c2be6efb91ed104aaeecd3e8dbe6abba785834e55d738475644b7167cdd557
Tx public key: b89d2f713bc4a9e9d057e0ef67dacf8e4fd7cdc182361ebe05bfe786eb16a1a9
| Timestamp: 1779455880 | Timestamp [UTC]: 2026-05-22 13:18:00 | Age [y:d:h:m:s]: 00:017:13:22:36 |
| Block: 383 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7513 | RingCT/type: yes/0 |
| Extra: 01b89d2f713bc4a9e9d057e0ef67dacf8e4fd7cdc182361ebe05bfe786eb16a1a902090000000393369e7d00 | ||
1 output(s) for total of 35.158745815335 HMNY
| stealth address | amount | amount idx | tag |
| 00: a1094f0b2253847ec8f2a649b4a659653ac8b7c9cd22419ef8cd4d43cd718659 | 35.158745815335 | 381 of 0 | <de> |
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": 443,
"vin": [ {
"gen": {
"height": 383
}
}
],
"vout": [ {
"amount": 35158745815335,
"target": {
"tagged_key": {
"key": "a1094f0b2253847ec8f2a649b4a659653ac8b7c9cd22419ef8cd4d43cd718659",
"view_tag": "de"
}
}
}
],
"extra": [ 1, 184, 157, 47, 113, 59, 196, 169, 233, 208, 87, 224, 239, 103, 218, 207, 142, 79, 215, 205, 193, 130, 54, 30, 190, 5, 191, 231, 134, 235, 22, 161, 169, 2, 9, 0, 0, 0, 3, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}