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: de0df8a92a9207b5b4d814b32276c3bd51993c6afcc71fef394a573ee04a4397
Tx prefix hash: fe23a45846e18dffba1395b57de200ed624dd3b1253d5051ee431541bf344b3b
Tx public key: 363ab3dca7c20968f0b1e66cbaffa02d38610ad43fe56e35424eb859276584f3
| Timestamp: 1779780579 | Timestamp [UTC]: 2026-05-26 07:29:39 | Age [y:d:h:m:s]: 00:013:19:10:57 |
| Block: 2101 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5795 | RingCT/type: yes/0 |
| Extra: 01363ab3dca7c20968f0b1e66cbaffa02d38610ad43fe56e35424eb859276584f302090000000226697be300 | ||
1 output(s) for total of 35.043725204228 HMNY
| stealth address | amount | amount idx | tag |
| 00: 1ddbcf307d42be0ffca4c0b07baa9164c46bcdba79c2e1a84c7d3a1ac405ecb0 | 35.043725204228 | 2419 of 0 | <b2> |
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": 2161,
"vin": [ {
"gen": {
"height": 2101
}
}
],
"vout": [ {
"amount": 35043725204228,
"target": {
"tagged_key": {
"key": "1ddbcf307d42be0ffca4c0b07baa9164c46bcdba79c2e1a84c7d3a1ac405ecb0",
"view_tag": "b2"
}
}
}
],
"extra": [ 1, 54, 58, 179, 220, 167, 194, 9, 104, 240, 177, 230, 108, 186, 255, 160, 45, 56, 97, 10, 212, 63, 229, 110, 53, 66, 78, 184, 89, 39, 101, 132, 243, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}