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: 4b94bc9efbe296df1cda53d718ab3af7d57ebdc084b614a361ffb5fc83d0c8b2
Tx prefix hash: 83d41bfee5447149141aa71c8cce5858a8586b87ce413f5c778c76a96ffebe04
Tx public key: 8cc47c08fc38b9119d61ff774e57013620cd29e83d813e4f293a4b159ef2c793
| Timestamp: 1780841752 | Timestamp [UTC]: 2026-06-07 14:15:52 | Age [y:d:h:m:s]: 00:005:21:05:13 |
| Block: 7471 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 1274 | RingCT/type: yes/0 |
| Extra: 018cc47c08fc38b9119d61ff774e57013620cd29e83d813e4f293a4b159ef2c793020900000002e49593ff00 | ||
1 output(s) for total of 34.686622760422 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2040055d530eaea39b7a82d1cefebba2cf0bd345a571faa35991d63102d3a2a0 | 34.686622760422 | 9203 of 0 | <22> |
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": 7531,
"vin": [ {
"gen": {
"height": 7471
}
}
],
"vout": [ {
"amount": 34686622760422,
"target": {
"tagged_key": {
"key": "2040055d530eaea39b7a82d1cefebba2cf0bd345a571faa35991d63102d3a2a0",
"view_tag": "22"
}
}
}
],
"extra": [ 1, 140, 196, 124, 8, 252, 56, 185, 17, 157, 97, 255, 119, 78, 87, 1, 54, 32, 205, 41, 232, 61, 129, 62, 79, 41, 58, 75, 21, 158, 242, 199, 147, 2, 9, 0, 0, 0, 2, 228, 149, 147, 255, 0
],
"rct_signatures": {
"type": 0
}
}