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: 0c841c38d621bcee893a7626067716920b008852f86d5036f22872ca20985fef
Tx prefix hash: 1f1e7d4dc9316bc66f42b710acfb2ad1acfd7860657cfaa27d3cb9c079114413
Tx public key: 1e1d1340189f7fb02b3f1a9065ebc8cca1c15cdc836c7ac6872274e09b7d2648
| Timestamp: 1779434217 | Timestamp [UTC]: 2026-05-22 07:16:57 | Age [y:d:h:m:s]: 00:017:17:29:50 |
| Block: 80 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0918 kB |
| Tx version: 2 | No of confirmations: 7806 | RingCT/type: yes/0 |
| Extra: 011e1d1340189f7fb02b3f1a9065ebc8cca1c15cdc836c7ac6872274e09b7d2648020900000001a662ed0300 | ||
1 output(s) for total of 35.179070883038 HMNY
| stealth address | amount | amount idx | tag |
| 00: d9a30dc6ff7b4a6c9b8181ef45ba07c9ded3ba0c36f4c7321892e42f913954f4 | 35.179070883038 | 76 of 0 | <1d> |
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": 140,
"vin": [ {
"gen": {
"height": 80
}
}
],
"vout": [ {
"amount": 35179070883038,
"target": {
"tagged_key": {
"key": "d9a30dc6ff7b4a6c9b8181ef45ba07c9ded3ba0c36f4c7321892e42f913954f4",
"view_tag": "1d"
}
}
}
],
"extra": [ 1, 30, 29, 19, 64, 24, 159, 127, 176, 43, 63, 26, 144, 101, 235, 200, 204, 161, 193, 92, 220, 131, 108, 122, 198, 135, 34, 116, 224, 155, 125, 38, 72, 2, 9, 0, 0, 0, 1, 166, 98, 237, 3, 0
],
"rct_signatures": {
"type": 0
}
}