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: 42022554018926e8a9069ab588b1dab8b1cae25496de99ece875a1e245ff9043
Tx prefix hash: 332bdcc447d77b4ae2ad9b335272657547f7fc46c13833f0f73d2dae2c6667ad
Tx public key: 8ecb089a028daccbe98df23ec408900154a52a2ab7c04d74e37e186cc7a1d1f3
| Timestamp: 1779796031 | Timestamp [UTC]: 2026-05-26 11:47:11 | Age [y:d:h:m:s]: 00:013:13:48:46 |
| Block: 2267 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 5619 | RingCT/type: yes/0 |
| Extra: 018ecb089a028daccbe98df23ec408900154a52a2ab7c04d74e37e186cc7a1d1f302090000000126697be300 | ||
1 output(s) for total of 35.032631410173 HMNY
| stealth address | amount | amount idx | tag |
| 00: 2c29bcbeaa71369c21ae5fdee7f6c8d7d27d3600ca7895c7fe56eec2e7893a7b | 35.032631410173 | 2635 of 0 | <9a> |
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": 2327,
"vin": [ {
"gen": {
"height": 2267
}
}
],
"vout": [ {
"amount": 35032631410173,
"target": {
"tagged_key": {
"key": "2c29bcbeaa71369c21ae5fdee7f6c8d7d27d3600ca7895c7fe56eec2e7893a7b",
"view_tag": "9a"
}
}
}
],
"extra": [ 1, 142, 203, 8, 154, 2, 141, 172, 203, 233, 141, 242, 62, 196, 8, 144, 1, 84, 165, 42, 42, 183, 192, 77, 116, 227, 126, 24, 108, 199, 161, 209, 243, 2, 9, 0, 0, 0, 1, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}