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: 6e21b1cd3218bb0a4a7d579c37d98724364f78b447561d53c3775738d89c4085
Tx prefix hash: 1ad8c68baeb08baa0417abfecfa549932e5deae6204f097340a07d2152006204
Tx public key: 3c08a4810057faeb3470e014d375bd7c7c7048ab8908db0f68b28adc411c6be0
| Timestamp: 1780083676 | Timestamp [UTC]: 2026-05-29 19:41:16 | Age [y:d:h:m:s]: 00:010:07:08:32 |
| Block: 4790 | Fee (per_kB): 0.000000000000 (0.000000000000) | Tx size: 0.0928 kB |
| Tx version: 2 | No of confirmations: 3119 | RingCT/type: yes/0 |
| Extra: 013c08a4810057faeb3470e014d375bd7c7c7048ab8908db0f68b28adc411c6be002090000000226697be300 | ||
1 output(s) for total of 34.864450785936 HMNY
| stealth address | amount | amount idx | tag |
| 00: 21e671344b174d92fff7e0d8a4bacbc273617d7a7aa7c4d1f61f5d5bd566e4c1 | 34.864450785936 | 6023 of 0 | <bf> |
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": 4850,
"vin": [ {
"gen": {
"height": 4790
}
}
],
"vout": [ {
"amount": 34864450785936,
"target": {
"tagged_key": {
"key": "21e671344b174d92fff7e0d8a4bacbc273617d7a7aa7c4d1f61f5d5bd566e4c1",
"view_tag": "bf"
}
}
}
],
"extra": [ 1, 60, 8, 164, 129, 0, 87, 250, 235, 52, 112, 224, 20, 211, 117, 189, 124, 124, 112, 72, 171, 137, 8, 219, 15, 104, 178, 138, 220, 65, 28, 107, 224, 2, 9, 0, 0, 0, 2, 38, 105, 123, 227, 0
],
"rct_signatures": {
"type": 0
}
}