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: 4144aa6ef45aec523e3c59a4e915de0b50c7335e324648d3fe0b5e19479159c7
Tx prefix hash: 3e1b6a9b0671f5447ec1b1306fe1d2e27db97dab774d3517de45dcb97c27b0e7
Tx public key: b801be2e4b2dbb911eb6b08a433629eb5ba8006476e503f6dc633a07fc05e024
| Timestamp: 1779454032 | Timestamp [UTC]: 2026-05-22 12:47:12 | Age [y:d:h:m:s]: 00:017:12:48:45 |
| Block: 361 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 7525 | RingCT/type: yes/0 |
| Extra: 01b801be2e4b2dbb911eb6b08a433629eb5ba8006476e503f6dc633a07fc05e02402090000000193369e7d00 | ||
1 output(s) for total of 35.160221167383 HMNY
| stealth address | amount | amount idx | tag |
| 00: 65aa7ee63db99aa6f5484069216aab3bcec9142622b7d93f309d5f288e8c56c9 | 35.160221167383 | 357 of 0 | <da> |
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": 421,
"vin": [ {
"gen": {
"height": 361
}
}
],
"vout": [ {
"amount": 35160221167383,
"target": {
"tagged_key": {
"key": "65aa7ee63db99aa6f5484069216aab3bcec9142622b7d93f309d5f288e8c56c9",
"view_tag": "da"
}
}
}
],
"extra": [ 1, 184, 1, 190, 46, 75, 45, 187, 145, 30, 182, 176, 138, 67, 54, 41, 235, 91, 168, 0, 100, 118, 229, 3, 246, 220, 99, 58, 7, 252, 5, 224, 36, 2, 9, 0, 0, 0, 1, 147, 54, 158, 125, 0
],
"rct_signatures": {
"type": 0
}
}